pomerium/internal/telemetry
Denis Mishin d9412f957a
metrics: don't add units and scope tags to prometheus metrics (#5749)
## Summary

With metrics now going via OTEL -> Prometheus exporter, there were
couple issues:

- some newer metrics had non-standard units that ended up in metric
names like `pomerium_storage_global_cache_hits__hit__total`
- we had three additional tags (`otel_scope_name`,
`otel_scope_schema_url`, `otel_scope_version`) added to each metric,
which do not really carry much meaningful information for us and expand
metric cardinality.

This PR reverts those two changes and updates the prometheus exporter.

## Related issues

Related: https://github.com/open-telemetry/opentelemetry-go/issues/7039

## User Explanation

<!-- How would you explain this change to the user? If this
change doesn't create any user-facing changes, you can leave
this blank. If filled out, add the `docs` label -->

## Checklist

- [x] reference any related issues
- [ ] updated unit tests
- [x] add appropriate label (`enhancement`, `bug`, `breaking`,
`dependencies`, `ci`)
- [x] ready for review
2025-07-24 14:34:11 -04:00
..
metrics metrics: don't add units and scope tags to prometheus metrics (#5749) 2025-07-24 14:34:11 -04:00
prometheus upgrade to go v1.24 (#5562) 2025-04-02 15:53:09 -06:00
component.go telemetry: backport component (#5655) 2025-06-16 13:10:51 -04:00
doc.go
http.go Fix IdP client metrics (#2810) 2021-12-08 13:22:53 -05:00
metrics.go telemetry: backport component (#5655) 2025-06-16 13:10:51 -04:00
util.go config: support multiple running services in addition to all-in-one mode (#5656) 2025-07-21 14:28:31 -06:00
util_test.go config: support multiple running services in addition to all-in-one mode (#5656) 2025-07-21 14:28:31 -06:00