micrometer-metrics/micrometer

micrometer cloudwatch should publish StatisticSet when any aggregations are done client side.

Open

#1,784 opened on Jan 10, 2020

View on GitHub
 (3 comments) (1 reaction) (0 assignees)Java (4,220 stars) (935 forks)batch import
enhancementhelp wantedregistry: cloudwatch

Description

Micrometer cloudwatch current publishes separate metrics for a Timer under different prefixes (avg, count, sum, max). Since Cloudwatch also does statistical aggregations this makes the client side aggregations a deterrent to being able to use the full capabilities of cloudwatch. Aggregation in itself is not a bad thing, but it needs to be sent to cloudwatch as an aggregation via a StatisticSet.

Contributor guide

Tech stack
java
Domain
backendcloud
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understanding of Micrometer's CloudWatch moduleKnowledge of CloudWatch StatisticSet
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Investigate the Micrometer CloudWatch module implementation, specifically how Timer metrics are currently published. Identify where separate metric prefixes (avg, count, sum, max) are created and how to aggregate them into a StatisticSet. Consider the CloudWatch API documentation for StatisticSet. Look for existing discussions or PRs in the micrometer repository that address this issue. Files likely include micrometer cloudwatch module's MeterRegistry and Timer publishing classes.