Open timbussmann opened 9 months ago
Does the NServiceBus.Metrics package expose the metrics via OpenTelemetry by default, or does it require custom code?
@cjoergensen, the Metrics package was designed before the advent of OTel. It requires custom code to capture and report those metrics to an OpenTelemetry collector. I'm not sure the data exposed by the Metrics package have all the needed information to plugin into the OTel activities model.
More details in our documentation.
FYI, stay tuned! Great things are on the way according to David Boike!
https://github.com/Particular/docs.particular.net/issues/6446#issuecomment-1934468629
Workaround to get these metrics in App Insights without the need for NServiceBus.Metrics: https://docs.particular.net/samples/open-telemetry/application-insights/
And Prometheus: https://docs.particular.net/samples/open-telemetry/prometheus-grafana/
Describe the suggested improvement
The NServiceBus OpenTelemetry integration currently promotes the following metrics:
The NServiceBus.Metrics package supports more metrics though, for example
These metrics are currently not available when using the OpenTelemetry integration instead of the Metrics package. When using OpenTelemetry, it does only add noise and overhead to also rely on the NServiceBus.Metrics package for these additional metrics.
Describe the suggested solution
Add additional metrics to the built-in OpenTelemetry metrics, e.g. Critical time and processing time.
Additional Context
No response