micrometer-metrics/micrometer

Refinement/Clarification of LongTaskTimer when using Prometheus

Closed

#6,507 opened on Jul 3, 2025

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Java (1,131 forks)batch import
doc-updatehelp wantedregistry: prometheus

Repository metrics

Stars
 (4,882 stars)
PR merge metrics
 (Avg merge 1d 21h) (100 merged PRs in 30d)

Description

Please describe the feature request

Following a question in Slack with @shakuzen https://micrometer-metrics.slack.com/archives/C662HUJC9/p1751460825070189

The Migration to Prometheus 1.x client libs in micrometer 1.13. changed the behaviour for LongTaskTimer.

Specifically in said Slack thread it was concluded that:

  • The migration guide could be more precise in outlining two distinct changes
    • Histogram -> GaugeHistogram for LongTaskTimers with histogram buckets.
    • No more active or duration suffix. _active_count -> _count or _gcount, _duration_sum -> _sum or _gsum
  • The docs for LongTaskTimer or Micrometer Prometheus docs don't make it clear that .publishPercentileHistogram() might be necessary for certain use cases
  • Consider making all LongTaskTimers produce HistogramGauges and ditch Summary due to the semantic mismatch

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.