It's been a breath of fresh air this summer to pull out New Relics agent libraries from several of our apps and have them replaced with OpenTelemetry dittos with auto-instrumentation turned off.
No more outages because NR's .NET agent generates code at runtime that causes segfaults. No more outages from the JS agent leaking memory if you instrument long-running functions. No more junior python devs spending days chasing the wrong call path because the Python agent produces bogus timing data on async python..
Just a dumb thing where we can ask for important flows to be traced and set up simple metrics for the things we want to keep track of.
Now we can keep using NRs dashboards, NRQL etc backend systems, which IMO are really good, without the downside of monthly outages each time we update an NR agent library.
That is super interesting. I'm curious if you'd be interested in sharing more about your .NET experience with OpenTelemetry? There's really not a lot of writing out there, good or bad, about experiences with OTel on .NET
OTEL on .NET has been "meh". I'm considering ripping out all of the metrics components in favor of Prometheus-net.
It's missing basic stuff it should have. For example, .NET auto uses a trace id when returning `Problem` or similar using Activity.Id. The trace id in OTEL is different for whatever reason, which means you have to add a customization in order to match the trace ids.
It doesn't keep track of http codes, routes, etc.
It's lacking basic functionality and outside of tracing is practically useless.
No more outages because NR's .NET agent generates code at runtime that causes segfaults. No more outages from the JS agent leaking memory if you instrument long-running functions. No more junior python devs spending days chasing the wrong call path because the Python agent produces bogus timing data on async python..
Just a dumb thing where we can ask for important flows to be traced and set up simple metrics for the things we want to keep track of.
Now we can keep using NRs dashboards, NRQL etc backend systems, which IMO are really good, without the downside of monthly outages each time we update an NR agent library.