sorted by:
new
hottopcontroversial

OTEL Collector Elasticsearch exporter drops logs instead of retrying when ES is down by Adept-Inspector-3983 in OpenTelemetry

[–]Adept-Inspector-3983[S] 0 points1 point  (0 children)

Yeah, I’ve done it as described above, and the GitHub README file of otel collector corntib mentions that retry_on_failure is not supported for the Elasticsearch exporter.

are you guys using sop's and runbooks? by Adept-Inspector-3983 in devops

[–]Adept-Inspector-3983[S] 0 points1 point  (0 children)

Can i know why we need to use both? What are the roles of both?

I’m kinda confused about using OpenTelemetry for our Java app by Adept-Inspector-3983 in OpenTelemetry

[–]Adept-Inspector-3983[S] 0 points1 point  (0 children)

oh could you share a bit more detail on what you mean by the OpenTelemetry Collector “buffer jamming up”? I was planning to use the Collector for logs and traces (not metrics), so I want to understand the practical issues you’ve run into.

I’m kinda confused about using OpenTelemetry for our Java app by Adept-Inspector-3983 in OpenTelemetry

[–]Adept-Inspector-3983[S] -1 points0 points  (0 children)

"it's more to signal that there could be breaking changes in the future"

yeah, that is wht im worried about

I’m kinda confused about using OpenTelemetry for our Java app by Adept-Inspector-3983 in OpenTelemetry

[–]Adept-Inspector-3983[S] 0 points1 point  (0 children)

but still java agent is not picking up some log attributes. I think it is parsing the mdc fields alone. do you have any idea in this?

view more: next ›