prometheus / prometheus/alertmanager

Allow comment log per silence

Open
#462 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component/silences component/storage component/ui kind/enhancement
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.