When forwarding the full journal of a linux host to stack driver, the character '@' in some of the systemd unit names produced errors with stack driver.
The '@' signs in log names for stack driver should be transcribed to the valid char set.
Should log all units, even those with a '@' sign in their name.
Your Environment
I use the following config:
[INPUT]
name systemd
tag host.*
DB /var/lib/fluent-bit/journal.db
[OUTPUT]
name stackdriver
match *
google_service_credentials /path/to/credentials.json
resource gce_instance
resource_labels instance_id=worker0,zone=hosteurope
I am unable to get most of the logs relating to postfix and other systemd units that use '@' in their unit names into my central log repository in google cloud stack driver logging.
Just changing the '@' sign to something like 'AT' would help a lot as one would be able to see these log entries in the central log and filter on them.
Bug Report
When forwarding the full journal of a linux host to stack driver, the character '@' in some of the systemd unit names produced errors with stack driver.
The '@' signs in log names for stack driver should be transcribed to the valid char set.
Just forward all the logs to google stack driver.
Expected behavior
Should log all units, even those with a '@' sign in their name.
Your Environment
I use the following config:
Additional context
I am unable to get most of the logs relating to postfix and other systemd units that use '@' in their unit names into my central log repository in google cloud stack driver logging.
Just changing the '@' sign to something like 'AT' would help a lot as one would be able to see these log entries in the central log and filter on them.