-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynamic application names #10
Comments
That's an interesting use case and I would love to support it. However I can't really come up with another solution than expanding the Do you use the RFC 5424 formatter? Because if you do, you could consider using STRUCTURED DATA for this, I just recently added support for it. You could then either use the Tell me what you think about it. |
Hi @schlagert thanks for having a look. I also couldn't come up with a different ideas as well, when I was looking through the code. I did have a look at the STRUCTURED DATA since I'm using syslog-ng which can listen for RFC5424 messages. According to this documentation the Since I'm using I didn't know about |
The packing the application name into the STRUCTURED DATA and then getting syslog-ng to rewrite the PROGRAM name worked perfectly thanks! |
A useful feature in
syslog
would be the ability to have more control over the application name when sending messages.For example if I had the apps
foo
,bar
andbaz
I'd like to get log messages like thisas opposed to this
The current behavior is to have the name set via either the env var, node name or
beam
. The specific use case we'd use it for is when we want each app in a release to log with their own name rather than a single name. This makes it easier to track where errors are happening in code, especially since we also forward WARNING messages and above to our monitoring tools.The text was updated successfully, but these errors were encountered: