You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My application logs was written to file system and then in Fluentd configMap, we changed the source file location to a different directory from /var/log/containers;
Fluentd reads from files system for example /var/mylogs/*.log and writes logs to CloudWatch without adding kubernetes attribute
Currently I am using Fluentd to cloudwatch plugin: v1.16.2-debian-cloudwatch-1.0.
Please advise if there is a way to have kubernetes attribute by updating Fluentd configuration.
This is an example when the application write logs to standard output inside /var/log/containers/.log;
but when Fluentd read the logs from /var/mylogs/.log, it doesn't include kubernetes attribute.
No response
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days
This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days
Describe the bug
My application logs was written to file system and then in Fluentd configMap, we changed the source file location to a different directory from /var/log/containers;
Fluentd reads from files system for example /var/mylogs/*.log and writes logs to CloudWatch without adding kubernetes attribute
Currently I am using Fluentd to cloudwatch plugin: v1.16.2-debian-cloudwatch-1.0.
Please advise if there is a way to have kubernetes attribute by updating Fluentd configuration.
This is an example when the application write logs to standard output inside /var/log/containers/.log;
but when Fluentd read the logs from /var/mylogs/.log, it doesn't include kubernetes attribute.
No response
The text was updated successfully, but these errors were encountered: