Agent logging policy #4886
Unanswered
gsmirnov-splk
asked this question in
Q&A
Replies: 1 comment 2 replies
-
hi @gsmirnov-splk! upstream otel exporters log connectivity issues at warning level (with some throttling) in the microsoft disto exporter, we log right away on first warning, and then aggregate and log at most every 5 minutes to minimize log spam (AggregatingLogger.java) |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi team, is there any generally accepted logging policy for otel instrumentation agents?
I understand that this is a trade-off between not polluting application logs and capturing useful agent info. For example, I was recently troubleshooting an agent connectivity issue. Until I enabled debug logs, the agent had logged zero complaints. With debug logs, the problem became immediately clear: the plain HTTP endpoint URL was specified with
https://
protocol. So I created this issue: signalfx/splunk-otel-java#566 that started some discussion around the subject. I'd love to hear more about this.Beta Was this translation helpful? Give feedback.
All reactions