Skip to content

Commit 4821c5a

Browse files
adinauerclaude
andcommitted
docs(micrometer): Clarify FunctionTimer limitations
Explain that FunctionTimer exposes cumulative count and total time rather than individual duration observations. Remove the unsafe weighted-mean guidance because independently reset streams may cover different observation windows. Co-Authored-By: Claude <noreply@anthropic.com>
1 parent 032ceb3 commit 4821c5a

1 file changed

Lines changed: 3 additions & 4 deletions

File tree

‎sentry-micrometer/README.md‎

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -47,10 +47,9 @@ The first successful finite function-meter poll establishes its baseline and emi
4747
positive deltas are sent. A decreasing value is treated as a reset and establishes a new baseline.
4848
`FunctionTimer` tracks its count and total-time baselines independently.
4949

50-
A `FunctionTimer` does not expose individual durations, so the integration emits neither a
51-
mean gauge nor a distribution. To derive a correctly weighted mean across instances, divide the
52-
sum of `${name}.total_time` by the sum of `${name}.count`. Percentiles cannot be derived from these
53-
cumulative values.
50+
A `FunctionTimer` exposes only cumulative count and total time, not individual duration
51+
observations. The integration therefore exports these values as counter deltas rather than a mean
52+
gauge or distribution. Percentiles cannot be reconstructed from count and total time alone.
5453

5554
Unsupported custom meters remain readable through Micrometer but are not exported to Sentry.
5655

0 commit comments

Comments
 (0)