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
Bugs should be filed for issues encountered whilst operating logging-operator.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors. #logging-operator
Please provide as much detail as possible.
Describe the bug:
ClusterFlow exclude logs feature is not working properly. Even after excluding the logs with the help of labels, container names I can see the logs pushed to the output.
Expected behaviour:
All the labels, namespaces and container_names mentioned in match.exclude[] should not be present in the log destination
Steps to reproduce the bug:
Use default logging Operator config.
Do you have any other clusterflows in the system? Based on the above ClusterFlow you should not get any logs at all, since there should be at least a 'select: {}' rule at the end.
Describe the bug:
ClusterFlow exclude logs feature is not working properly. Even after excluding the logs with the help of labels, container names I can see the logs pushed to the output.
Expected behaviour:
All the labels, namespaces and container_names mentioned in match.exclude[] should not be present in the log destination
Steps to reproduce the bug:
Use default logging Operator config.
Additional context:
Add any other context about the problem here.
Environment details:
/kind bug
The text was updated successfully, but these errors were encountered: