You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TracerConverter implementation should automatically decorate a resolver Tracer with the metrics capability.
One issue to consider is how best to obtain the MetricsReporter implementation and how it will be configured.
For example, the PrometheusMetricsReporter does not expose an endpoint for collection (scraping) of the metric data - this is left to the application, which may be using Prometheus to collect other metrics, and/or want to decide how best to expose (or push) the metrics.
When the TracerResolver/Converter approach is being used, it likely that the application may not be aware of the tracing or metrics collection - therefore an additional mechanism will be required to enable the appropriate metrics endpoint to be initialized.
The text was updated successfully, but these errors were encountered:
The
TracerConverter
implementation should automatically decorate a resolverTracer
with the metrics capability.One issue to consider is how best to obtain the
MetricsReporter
implementation and how it will be configured.For example, the
PrometheusMetricsReporter
does not expose an endpoint for collection (scraping) of the metric data - this is left to the application, which may be using Prometheus to collect other metrics, and/or want to decide how best to expose (or push) the metrics.When the
TracerResolver/Converter
approach is being used, it likely that the application may not be aware of the tracing or metrics collection - therefore an additional mechanism will be required to enable the appropriate metrics endpoint to be initialized.The text was updated successfully, but these errors were encountered: