.NET 6.0 OpenTelemetry Metrics

[Depechie]

With .NET 6 we should be able to use System.Diagnostics.Metrics to push OpenTelemetry metrics.
I tried to set this up with guidence of this repository about using the Elastic stack, my take on it is pushed here : https://github.com/Depechie/OpenTelemetryElastic

But I'm not getting any metrics visible in Kibana. The OpenTelemetry tracing is working fine though, so the setup of the apm server and OpenTelemetry Collector is correct I guess.

Did you try this already?
I just wanted to try to visualize a counter : https://github.com/Depechie/OpenTelemetryElastic/blob/main/OpenTelemetryElastic/Controllers/WeatherForecastController.cs#L31

[damikun]

With .NET 6 we should be able to use System.Diagnostics.Metrics to push OpenTelemetry metrics.

I tried to set this up with guidence of this repository about using the Elastic stack, my take on it is pushed here : https://github.com/Depechie/OpenTelemetryElastic

But I'm not getting any metrics visible in Kibana. The OpenTelemetry tracing is working fine though, so the setup of the apm server and OpenTelemetry Collector is correct I guess.

Did you try this already?

I just wanted to try to visualize a counter : https://github.com/Depechie/OpenTelemetryElastic/blob/main/OpenTelemetryElastic/Controllers/WeatherForecastController.cs#L31

Hi, How are you exporting metrics? Using direct otel to elastic or using collector between? In case of colector it require some setup in collector config file to resend this data to elastic..

[Depechie]

No luck with the direct link either. But to be honest, I'm new to Kibana too, so not sure if I sill need to set thing correctly there? Although tracing came automatically visible.

[damikun]

Usually you don't need to setup index but sometimes I did that since it was not working.. Basically all traces can be query in root elastic query (out of Tracing/APM view) so all this record should be visible using standard query first. I will have a look on this in upcoming work week..

[Depechie]

Seems it was working! If I go to the discovery part of Kibana, you can filter on incoming data and the metrics with the requestcounter ARE there.
Only not default in the Observability/Metrics area ( not sure why ).
The details I found here https://www.elastic.co/guide/en/apm/get-started/current/open-telemetry-elastic.html#open-telemetry-elastic-verify

Other thing I now notice is that the counter is not gradually increasing although I have set it up as a singleton.

[damikun]

Super.. As i said sometimes it is required that the index pattern needs to be created manually and than set in APM for example.. Apm use by default multiple patterns and maybe this is missing inside by default.. Or maybe your indexed values does not follow some default pattern..

[damikun]

https://github.com/damikun/trouble-training/blob/main/Doc/Assets/kibana_add_index_pattern.png

[Depechie]

Not sure why, but suddenly the RequestCounter ( is the name of the counter I gave in the .NET web api ) is also selectable in the metrics explorer.
I did not add the index myself, but I did try some things in the data discovery dashboard.

Still the sum seems off somehow. But anyhow the data was already flowing through from the get go it seems :D

[Depechie]

Ha nevermind, I guess the field was indeed added to the index! I guess because I selected it in the data discovery graph as filter.
Thx for you link, I did not know I could see what the current index was!