-
The real issue I'm facing is that I can't find a way to troubleshoot this further, I've enabled detailed logging but it's not giving me any information on how my journald logs are being processed. I'm expecting to be able to access the value for one of the key/value pairs(_HOSTNAME: server1) in the json data for a given log and use it to add a custom attribute (hostname: server1) This is what my configuration looks like currently:
Any tips on how to troubleshoot the processing of my logs would be appreciated, in this case being able to see what elements are available and under what namespace would be helpful, is body._HOSTNAME even being looked up and just missed because I don't have the correct namespace? When written out to file the logs look something like the below, logs viewed in Grafana using Loki as the datasource are also not how I'd like them to appear, all of my fields like _HOSTNAME and MESSAGE appear nested under a body element but this is secondary to my main question. Below this I'll include a screenshot of the messages in Grafana to show what I mean just in case someone has any ideas.
|
Beta Was this translation helpful? Give feedback.
See open-telemetry/opentelemetry-collector-contrib#34808