DramatiqTemporalPrometheus

Prometheus metric descriptor registration conflicts in Temporal Server

warning
configurationUpdated May 10, 2024
How to detect:

When starting Temporal development server, Prometheus reporter errors occur due to duplicate descriptor registrations with inconsistent schemas. The AccessHistoryOld counter is registered multiple times with different label orderings, preventing proper metric collection.

Recommended action:

Review Prometheus metric initialization in Temporal Server configuration. The duplicate registrations indicate metrics are being initialized multiple times with varying label definitions. This may result in incomplete metrics collection. Check for configuration issues or report as bug to Temporal team.