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
The collector supports emitting its internal logs via OTLP. After testing this functionality, it appears that logs of all severities are emitted via the logger provider configured. This is because the otelzap bridge doesn't have a configuration for severity level. This requires a separate processor (minsev) which is currently not supported by the otel configuration schema.
I will submit a pull request that proposes wrapping the Tee'd zap core into another zap core that will apply the filtering before logs are sent to the logger provider.
The text was updated successfully, but these errors were encountered:
The collector supports emitting its internal logs via OTLP. After testing this functionality, it appears that logs of all severities are emitted via the logger provider configured. This is because the otelzap bridge doesn't have a configuration for severity level. This requires a separate processor (minsev) which is currently not supported by the otel configuration schema.
I will submit a pull request that proposes wrapping the Tee'd zap core into another zap core that will apply the filtering before logs are sent to the logger provider.
The text was updated successfully, but these errors were encountered: