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
disabling collection for specific units, only enabling it for specific units, etc.
customizing the collected data - decorating with metadata, filtering, etc.
This might (and hopefully should) result in changes to configuration of the collection, so that the common use cases do not force the user to mess with the raw OTC configuration, or even prevent that configuration from being exposed in the values.yaml file.
The text was updated successfully, but these errors were encountered:
The ability to gather kernel messages would be fantastic too - they have no "unit" so they kinda fall through the gaps there. In particular, gathering the logs generated by IPTables "LOG" rules and being able to enrich the logs the log prefix and level would be amazing!
Use case - Calico, and I suspect other k8s network policy engines, create underlying IPTables rules to implement the network policy.
We need high-level documentation for collecting systemd logs, akin to https://github.com/SumoLogic/sumologic-kubernetes-collection/blob/v2.11.0/deploy/docs/collecting-kubernetes-events.md for collecting Kubernetes events.
It should describe the frequent use cases, like:
This might (and hopefully should) result in changes to configuration of the collection, so that the common use cases do not force the user to mess with the raw OTC configuration, or even prevent that configuration from being exposed in the
values.yaml
file.The text was updated successfully, but these errors were encountered: