Skip to content

Use a Timer for the sinkRequestLatency to report it with time units#6510

Merged
dlvenable merged 1 commit intoopensearch-project:mainfrom
dlvenable:sinkRequestLatency-timer
Feb 16, 2026
Merged

Use a Timer for the sinkRequestLatency to report it with time units#6510
dlvenable merged 1 commit intoopensearch-project:mainfrom
dlvenable:sinkRequestLatency-timer

Conversation

@dlvenable
Copy link
Copy Markdown
Member

Description

The sinkRequestLatency metric is using DistributionSummary. This means that Micrometer will not report units. This PR changes this to a Timer so that it includes time units.

Adds a new method to record with time units. Retains the existing method for double. Update usage of this as well.

Per Micrometer documentation:

A Timer is really a specialized distribution summary that is aware of how to scale durations to the base unit of time of each monitoring system and has an automatically determined base unit. In every case where you want to measure time, you should use a Timer rather than a DistributionSummary.

This is an alternative solution to the problem identified in #6508.

Issues Resolved

N/A

Check List

  • New functionality includes testing.
  • New functionality has a documentation issue. Please link to it in this PR.
    • New functionality has javadoc added
  • Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

…rts it with correct units. Adds a new method to record with time units and retains the existing method for double. Update usage of this as well.

Signed-off-by: David Venable <dlv@amazon.com>
@dlvenable dlvenable merged commit 13bcfda into opensearch-project:main Feb 16, 2026
73 of 74 checks passed
@dlvenable dlvenable deleted the sinkRequestLatency-timer branch February 16, 2026 22:03
@dlvenable dlvenable added this to the v2.14 milestone Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking change Any change which may break existing configurations and deployments

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants