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
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always
frustrated when [...]
We have calico installed in our clusters. Network policies that log traffic correspond to kernel logs, .e.g SYSLOG_IDENTIFIER=kernel. Previously, we were able to do this with the fluent-bit config:
fluent-bit:
config:
inputs: |
[INPUT]
Name systemd
Systemd_Filter SYSLOG_IDENTIFIER=kernel
There doesn't appear to be a way to do this with otelcol
Describe the solution you'd like A clear and concise description of what you want to happen.
Otelcol config options to filter logs based on SYSLOG_IDENTIFIER exposed via helm value inputs
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always
frustrated when [...]
We have calico installed in our clusters. Network policies that log traffic correspond to kernel logs, .e.g
SYSLOG_IDENTIFIER=kernel
. Previously, we were able to do this with the fluent-bit config:There doesn't appear to be a way to do this with otelcol
Describe the solution you'd like A clear and concise description of what you want to happen.
Otelcol config options to filter logs based on SYSLOG_IDENTIFIER exposed via helm value inputs
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: