Grafana must also be configured to get the data from Promethus and visualize it as graphs. The Prometheus service must be configured to retrieve the metrics data from the endpoint. The diagram below shows the overall component interactions:Ī ->|Report Metrics| B(Prometheus Exporter)į -> |Poll Metrics| E # TYPE nservicebus_messaging_successes counter The raw metrics retrieved through the scraping endpoint look as follows: # HELP nservicebus_messaging_successes Total number of messages processed successfully by the endpoint. The HTTP endpoint is also exposed through a local IP address so the Prometheus service running in Docker can reach it over the network. To enable the Prometheus exporter, run the following code: In this sample, the service that exposes the data to scrape is hosted on http:/ / localhost:9185/ metrics. The exporter is available via a NuGet package OpenTelemetry. A Prometheus exporter can expose this data via an HTTP endpoint and the Prometheus service, hosted as a docker service, can retrieve and store this information. The metrics are gathered using OpenTelemetry standards on the endpoint and must be reported and collected by an external service. the exception type name (if applicable).NET fully-qualified type information for the message being processed the uniquely addressable address for the endpoint (if set). successesĮach reported metric is tagged with the following additional information: Number of successfully processed messages via nservicebus.Number of failed messages via nservicebus.Number of fetched messages via nservicebus.There are three metrics reported as a Counter, with the following keys: Var meterProviderBuilder = Sdk.CreateMeterProviderBuilder()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |