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
Is your feature request related to a problem? Please describe.
In the Specification of opentelemetry, I haven't seen this usage in any examples or conventions. But in opentelemetry-collecotor, the convention for obsreport metrics is /<metric_name>.
Describe the solution you'd like
Could you let me know whether the convention in opentelemetry-collecotor is consistent with the Specification of opentelemetry?
The text was updated successfully, but these errors were encountered:
I believe this is a side effect of the metrics having been initially instrumented using opencensus. You can see where support for / was added to the specification: open-telemetry/opentelemetry-specification#3422
See open-telemetry/oteps#238 for an OpenTelemetry Enhancement Proposal around semantic conventions for telemetry pipeline monitoring
The metrics generated have been moved to use _ as a separator. This makes the any metrics generated by the collector consistent regardless of whether the export is done via prometheus (which already did this automatically) or via another exporter (otlp, console).
Is your feature request related to a problem? Please describe.
In the Specification of opentelemetry, I haven't seen this usage in any examples or conventions. But in opentelemetry-collecotor, the convention for obsreport metrics is /<metric_name>.
Describe the solution you'd like
Could you let me know whether the convention in opentelemetry-collecotor is consistent with the Specification of opentelemetry?
The text was updated successfully, but these errors were encountered: