David Ashpole
David Ashpole
My understanding of https://github.com/open-telemetry/opentelemetry-specification/blob/v1.20.0/specification/metrics/api.md#instrument-name-syntax is that it is a restriction on the OTel SDK (despite being in the API document), since APIs accept strings, and validation is done in the...
@aknuds1 has thought about this as well I think. My 2c: We should probably always preserve all original opentelemetry resource attributes. Adding job and instance should be the optional part,...
@jade-guiton-dd this issue is about providing instrument-level configuration similar to other advisory parameters. If the Meter is disabled, no metrics will be collected, regardless of this setting. If the meter...
@lmolkova Interesting idea. I wonder if that should be a higher-level configuration concept, since we already have knobs for selecting which attributes are disabled by default. I would imagine that...
I started working on a prototype of this, but quickly realized that Aggregation is an SDK concept, and thus can't be used in the API without more invasive changes. Instead,...
A histogram would be useful if the job's scrape interval is less than the scrape interval of scraping the prometheus server's /metrics endpoint. A counter would let us compute the...