Stephan BehnkeandGitHub 91df0dcb4f Unify OTEL resource names (#7131) ...

## What changed?
<!-- Describe what has changed in this PR -->

Moved all telemetry resource names to one place.

## Why?
<!-- Tell your future self why have you made these changes -->

Having them in one place.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->

2025-01-23 16:58:28 +00:00

..

abstract_data_store_factory.go

Refactor fault injection package (#5886)

2024-05-10 17:47:36 -07:00

factory_test.go

Switch to uber gomock (#6493)

2024-09-09 14:44:20 -07:00

factory.go

Retry on DataLoss error from persistence layer (#6789)

2024-11-12 19:06:24 +00:00

fx.go

Unify OTEL resource names (#7131)

2025-01-23 16:58:28 +00:00

health_request_rate_limiter.go

Use typed dynamic configs (#5962)

2024-06-03 18:16:15 -07:00

persistence_rate_limited_clients_test.go

Switch to uber gomock (#6493)

2024-09-09 14:44:20 -07:00

quotas_test.go

Import alignment (#6426)

2024-08-23 14:48:10 -06:00

quotas.go

Different error message for per namespace per shard rate limiting (#6433)

2024-08-30 18:47:36 +00:00