prometheus / prometheus/alertmanager
Allow comment log per silence
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.6k
- Forks
- 2.5k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 61
Description
For long running silences it is feasible to have a log of comments rather than a single one to easily add information on the current status of an underlying problem.
This can be done within a single comment, but usually comments are fairly short and people might want to clarify. For that the silence creator is not necessarily the best reference.
I propose silence objects to have a list of <author, timestamp, comment>. Generally that will be so short that we can just store it within the same blob.
Semantics should be that you can add a comment to a silence by ID and have to provide an initial comment when creating the silence. Existing comments cannot be modified.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how silence objects are created, stored, and addressed by ID in the Alertmanager codebase. Define the behavior for requiring an initial comment, appending immutable author/timestamp/comment entries, and preserving existing silences; done means the API and persisted silence representation support the proposed comment-log semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100