aws / aws/eks-charts

[appmesh-prometheus] Too many metrics

Open
#1,064 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
Mustache
Stars
1.3k
Forks
1.1k
Avg merge
22m
Merged PRs (30d)
5

Description

**Is your feature request related to a problem?**
Apparently enabling `remote_write` (See https://github.com/aws/eks-charts/pull/978) and sending all these metrics to New Relic made our bill increase by like 6x.

**Is your feature request related to a specific Helm chart, if yes mention name of the chart?**
appmesh-prometheus

**Describe the solution you'd like**
How can we configure the metrics we want? Do we need to make a new PR that allows writing the entire `prometheus.yml`?

**Describe alternatives you've considered**
Forking and maintaining our own version of the helm chart sounds annoying.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the appmesh-prometheus Helm chart and how its remote_write settings are currently configured. Determine what chart configuration would let users select the metrics sent to New Relic, and consider the issue resolved when that configuration is clearly defined and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, prometheus
Domain
devops, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.