Closed miyunari closed 12 months ago
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This errors is fired up, because probably there is no files in the specified directory.
I get the same if I run the command manually
➜ opentelemetry-collector-contrib git:(main) ✗ journalctl --utc --output=json --follow --unit firewalld --priority info --directory /run/log/journal
No journal boot entry found from the specified boot offset (+0)
➜ opentelemetry-collector-contrib git:(main) ✗ ls /run/log/journal
➜ opentelemetry-collector-contrib git:(main) ✗
It works fine if directory is unspecified
Thanks @sumo-drosiek! Actually the /run/log/journal
folder is empty and removing the directory
entry worked :smiley:
But I still wonder where the journal files are located. :no_good:
2023-10-24T11:06:34.560+0200 info LogsExporter {"kind": "exporter", "data_type": "logs", "name": "debug", "resource logs": 1, "log records": 2}
2023-10-24T11:06:34.561+0200 info ResourceLog #0
Resource SchemaURL:
ScopeLogs #0
ScopeLogs SchemaURL:
InstrumentationScope
LogRecord #0
ObservedTimestamp: 2023-10-24 09:06:34.377994896 +0000 UTC
Timestamp: 2023-10-24 09:06:34.081978 +0000 UTC
SeverityText:
SeverityNumber: Unspecified(0)
Body: Map({..., "JOB_TYPE":"start","MESSAGE":"Starting firewalld.service - firewalld - dynamic firewall daemon...","MESSAGE_ID":"7d4958e842da4a758f6c1cdc7b36dcc5","PRIORITY":"6","SYSLOG_FACILITY":"3","SYSLOG_IDENTIFIER":"systemd","TID":"1","UNIT":"firewalld.service","_BOOT_ID":"d0fae1980ca54d549daa9adfcf388ad7", ...})
Trace ID:
Span ID:
Flags: 0
@miyunari Probably /var/log/journal
. It should be somewhere in the systemd configuration :sweat_smile:
Component(s)
receiver/journald
What happened?
Description
In a first step I would like to read firewalld logs and print them via the collector to my console.
Steps to Reproduce
I downloaded the opentelemetry collector contrib binary.
Then I started it with my configuration:
Expected Result
See my journald logs in the opentelemetry collector logs.
Actual Result
Getting an error message, see log output.
Collector version
v0.86.0
Environment information
Environment
OS: Fedora 38
OpenTelemetry Collector configuration
Log output
Additional context
I checked that the unit is active
Using
journalctl -u firewalld
I also see some logs: