Mastodawn

(1/2) My first foray into OpenTelemetry was disappointing. The UI's and broken tools are a mess.

- Bad consistency
- Dozens of packages required
- Spans seem to work 50% of the time

Notice just "postgresql". No details. I have to expand it to see them. Compare with the second screenshot where I see ACTUAL details without needing to expand.

As for spans, look at that "=> 4.41s". If I'm using OT that should be a Span instead of polluting the log entries?

#dotnet #programming #opentelemetry

Show thread

Lloyd

(2/2) I did try a few approaches for this and saw the same inconsistencies and bad UX.

I tried Seq + OT + .NET, then I tried Seq + otel-collector + OT + .NET.

Finally, I tried Grafana + otel-collection + OT + .NET.

I was reminded of why I avoid Grafana, both the company and the product. It might look nice visually, if you can set it up and if you can find the will to maintain some spaghetti setup of Grafana and it's 10 required products and engines.