Closed jbennink closed 3 weeks ago
Hi @jbennink, thanks for reaching out.
There are two problems in your setup.
5341
, but your URLs are using 5431
, and/v1/traces
at the end of the URL (the same as the logs endpoint).Here's your sample running:
Not sure why ASP.NET Core is producing those messages without a ContentLength
property - the should include a ContentLength: null
but perhaps some optimization is wiping those out.
Seq 2024.3 doesn't support OTLP metrics so the metrics output will need to go to something like Prometheus or InfluxDB instead.
Hope this helps, Nick
@nblumhardt OMG, I'm so embarres right now. It's the url, the thing I keep copy pasting. This is why you need peer review :-O After changing both it worked immediately.
Describe the bug Once I set things up -- I think correctly -- I could net get traces to show in Seq. I made a small repro in github OpenTelemetryTestingDefaultIlogger based on the WeatherForecast WebApi template adding as little as possible to get it to work with OpenTelemetry.
P.S. This might not be a bug, but more some seup issue on my part but I scoured the web and could not find any better documentation of samples without them either being non complete or very hard to digest.
To Reproduce Steps to reproduce the behavior:
Expected behavior I would have expected to see a trace like I have seens in some screenshots but I could never find actual complete samples code of
the thing
Screenshots
Environment (please complete the following information):