David Ashpole
David Ashpole
From the [OpenMetrics spec on timestamps](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#exposing-timestamps): > In general, MetricPoint timestamps should not be exposed, as it should be up to the ingestor to apply their own timestamps to samples...
From the [prometheus spec](https://github.com/prometheus/docs/blob/main/content/docs/instrumenting/exposition_formats.md#histograms-and-summaries): > Each bucket count of a histogram named x is given as a separate sample line with the name x_bucket and a label {le="y"} (where y...
From the [OpenTelemetry to Prometheus spec for sums](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md#sums): > Monotonic Sum metric points MUST have _total added as a suffix to the metric name. The [current implementation](https://github.com/open-telemetry/opentelemetry-swift/blob/444d98193ded50927a37f87f12ae781e46e640f7/Sources/Exporters/Prometheus/PrometheusExporterExtensions.swift#L74) does not add...
From the [OpenTelemetry to Prometheus spec for gauges](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md#gauges-1): > An [OpenTelemetry Gauge](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/data-model.md#gauge) MUST be converted to a Prometheus Gauge. The [current implementation](https://github.com/open-telemetry/opentelemetry-swift/blob/main/Sources/Exporters/Prometheus/PrometheusExporterExtensions.swift#L39) emits gauges as summaries.
I did a mini-audit of the current state of prometheus exporters in the OTel ecosystem a little while back. I'm leaving a tracking issue here to be able to easily...
[Prometheus Unknown metrics](https://github.com/OpenObservability/OpenMetrics/blob/d99b705f611b75fec8f450b05e344e02eea6921d/specification/OpenMetrics.md#unknown) are metrics that have no type information, such as metrics from a third party system. Prometheus doesn't actually make use of type information, so Prometheus users can...
**Description:** Document the new feature gate added in the recent release of opentelemetry-operations-go, and also add general troubleshooting documentation based on recent issues opened for the component.
**Description:** Fixes https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/32814 It places the removal of replaced resource attributes (`net.host.name`, `net.host.port`, and `http.scheme`) behind a feature gate, `receiver.prometheusreceiver.RemoveLegacyResourceAttributes`, which is initially disabled by default. This means the current...
**What I would like to be able to do** I mentioned this briefly at the community meeting earlier today. As a general best practice, DaemonSets should avoid watching a resource...
As discussed during the community call today, the opentelemetry expiry only handles counters, and not histograms: https://github.com/grafana/beyla/blob/main/pkg/internal/netolly/export/otel/expirer.go#L54. This is because synchronous APIs in OTel do not have delete methods on...