We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I didn't find any option to change the logs output to different naming convention: instead of :
Jul 06 14:27:29 "POD" "POD-info": 2016/07/06 11:27:29 - message
to be (for example):
Jul 06 14:27:29 "service" "specific pod info"
The text was updated successfully, but these errors were encountered:
What logging are you talkiing about?
Sorry, something went wrong.
For example:
service (a.k.a nginx) specific pod info (a.k.a worker.{{ index }}) - stdout message.
After sone investigation I figure it out:
In order to make the logs per you naming convention you can use this in your yaml file (or use docker native commands):
yaml example:
env: - name: SYSLOG_TAG value: '{{ index .Container.Config.Labels "io.kubernetes.pod.namespace" }}[{{ index .Container.Config.Labels "io.kubernetes.pod.name" }}]' - name: SYSLOG_HOSTNAME value: '{{ index .Container.Config.Labels "io.kubernetes.container.name" }}'
One thing which is missing is the ENV variables support add env vars on SYSLOG_TAG template.
Hope it will be finished soon.
Yeah this sounds like not something related to logspout but actually whatever orchestration tool you are using.
Happy you got it resolved.
No branches or pull requests
Hi,
I didn't find any option to change the logs output to different naming convention:
instead of :
Jul 06 14:27:29 "POD" "POD-info": 2016/07/06 11:27:29 - message
to be (for example):
Jul 06 14:27:29 "service" "specific pod info"
The text was updated successfully, but these errors were encountered: