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 (935 forks)batch import
enhancementhelp wantedregistry: cloudwatch

Repository metrics

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

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

Research direction
Examine the micrometer cloudwatch module to understand how Timer metrics are published separately, then implement a change to aggregate them into a StatisticSet before publishing to CloudWatch.
Tech stack
java
Domain
backendobservability
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaMicrometerAWS CloudWatch
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60