-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Using kubernetes filter and cleaning log entry #9829
Labels
Comments
That's the conf I'm using:
|
Can you repeat with the OSS image latest version (3.2.4) and also using |
It worked once I've switched to the latest (3.2.4) and adding the log_key (I double checked and it doesn't work with the AWS image). Closing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
I tried adding the kubernetes filter so I can have the pod and container name as keys for using
log_stream_template $kubernetes['pod_name'].$kubernetes['container_name']
.I then tried using the
log_key log
so I can get only the actual logs in cloud watch, following the docs.It seems to break the log_stream_template since the keys are not there any more. I wanted a way to have only the log entries saved and not the whole kubernetes json, with a custom log stream name, based on the pod and container names.
Describe the bug
Mentioned above
To Reproduce
Use both the log_key and the log_stream_template in the cloudwatch output.
Expected behavior
Being able to set the custom name and remove all of the keys from the log.
Screenshots
NA
Your Environment
Additional context
The text was updated successfully, but these errors were encountered: