Skip to content
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

Fluentd logging agents should attach kubernetes labels to the logs they collect #4255

Closed
a-robinson opened this issue Feb 9, 2015 · 1 comment
Labels
area/introspection area/logging priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@a-robinson
Copy link
Contributor

All of the labels attached to the container whose logs are being collected should be added on to the logs. For example, if logs are being collected for container foo with the labels env=prod and service=backend, those labels (env=prod, service=backend) should be attached such that someone querying logs later can ask for all logs with those labels to easily aggregate across containers.

IIRC both elasticsearch and Google Cloud Logging support arbitrary labels, so the only work needed should be getting the container's labels into Fluentd and attaching them.

cc @satnam6502

@a-robinson
Copy link
Contributor Author

Closing in favor of #8001, which is effectively the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/introspection area/logging priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

3 participants