David Ashpole

Results 124 issues of David Ashpole

**What are you trying to achieve?** Prometheus is adding UTF-8 support to its metrics format and promql query language, largely to be compatible with OpenTelmetry naming. This could possibly require...

spec:miscellaneous

**Which issue(s) this PR fixes**: Part of https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/647-apiserver-tracing This meets the following KEP requirements: * Publish guidelines for kubernetes components on when and how to add tracing to a component....

cncf-cla: yes
approved
sig/instrumentation
size/M
area/developer-guide

Based on https://github.com/open-telemetry/opentelemetry-go/blob/main/.github/workflows/codeql-analysis.yml and https://github.com/open-telemetry/opentelemetry-python/blob/main/.github/workflows/codeql-analysis.yml

# Feature Request This may be a question for semantic conventions, but I figured I would start here. The k8s demo currently uses the `app.kubernetes.io/component` label as the `service.name` resource...

enhancement

### Problem Statement https://github.com/open-telemetry/opentelemetry-specification/pull/2951 defined an experimental MetricProducer interface, which can be used to support metric bridges. Note that the specifications are experimental, so it isn't critical that it is...

enhancement
help wanted
pkg:OpenTelemetry
metrics
spec-compliance

Now that https://github.com/open-telemetry/opentelemetry-specification/pull/2703 is released, we can update the prometheus exporter to make use of OpenTelemetry scope, particularly for reducing collisions between metrics with the same name. **Describe the solution...

metrics
roadmap review

From the spec for [handling resource in prometheus exporters](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md#resource-attributes-1): > In SDK Prometheus (pull) exporters, resource attributes SHOULD be converted to a single [target_info metric](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#supporting-target-metadata-in-both-push-based-and-pull-based-systems); otherwise, they MUST be dropped,...

metrics
roadmap review

From the [OTel prometheus spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md#metric-metadata-1): > The unit MUST be added as a suffix to the metric name, and SHOULD be converted to [base units](https://github.com/OpenObservability/OpenMetrics/blob/main/specification/OpenMetrics.md#units-and-base-units) recommended by OpenMetrics when possible....

metrics
roadmap review

From the [OpenTelemetry to Prometheus spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md#sums): > * If the aggregation temporality is cumulative and the sum is non-monotonic, it MUST be converted to a Prometheus Gauge. The current implementation...

metrics
roadmap review

The value of the +Inf bucket in a prometheus histogram is the count of the number of observations less than infinity, I.E. the `histogram.count`. The current implementation uses the count...

metrics
roadmap review