adobe / adobe/butler

butler metrics needs to be like guy pearce in memento

Open
#5 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
12
Forks
7
PR merge metrics
No merged PRs in 30d

Description

there is an issue with butler where if you have to manager sections (eg: prometheus, alertmanager), and butler will create prometheus metrics for both of those.

If you remove the configuration for one of the managers, then the prometheus metrics will still hang about, and that's bad.

@kirharri suggests that at each config retrieval iteration, then blow away all the metrics, and re-write them.

let's sort it out

Contributor guide

Open the contributing guide

Research direction

Start by tracing Butler's configuration retrieval iteration and the code that creates Prometheus metrics for each manager section. Done means metrics for removed manager configurations no longer remain, while metrics for active sections continue to be exposed.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, prometheus
Domain
observability-sre
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.