Skip to content

Overview Dashboard #5261

@siavashs

Description

@siavashs

Alertmanager Open Issues — Analysis Report

Executive Summary

  • 157 feature/enhancement requests dominate the backlog, vs 23 confirmed bugs.
  • 142 issues (43%) have had no activity for over a year; the median issue is 1218 days old.
  • 14 issues are blocked waiting on the reporter for more information.
  • 16 recurring themes account for clusters of overlapping/duplicate reports (see below).
  • The single largest driver is notification delivery: component/notify is the most-applied component label.

Overview by Category

Category Count %
Bug 23 7%
Documentation 15 5%
Cleanup / Tech-debt 2 1%
Feature / Enhancement 157 48%
Question 11 3%
Support 25 8%
Change / Proposal 1 0%
Friction 1 0%
Release / Packaging 1 0%
Uncategorized 91 28%
Total 327 100%

Overview by Component

Component Count
component/notify 68
component/ui 31
component/config 18
component/silences 17
component/api 14
component/high availability 12
component/templating 12
component/inhibition 4
component/cli 3
component/storage 3
component/dispatch 2
component/nflog 2

Most Up-voted Issues (by reactions)

Issue Reactions Comments Category
#2217 Support Block Kit with Slack notifications 187 24 Feature / Enhancement
#226 Send resolved notification for silenced alerts 103 70 Feature / Enhancement
#3221 Send subsequent notifications to a slack thread instead of channel 48 14 Feature / Enhancement
#1860 Feature request: provide a way to acknowledge a firing alert 44 27 Feature / Enhancement
#730 Silence notifications 44 14 Feature / Enhancement
#2940 Add google chat receiver 42 17 Feature / Enhancement
#3503 [Feature] Support adaptive cards for MSTeams 34 11 Feature / Enhancement
#2556 Darkmode 34 2 Uncategorized
#1496 Templating support for body of webhook_config 34 8 Feature / Enhancement
#2165 Feature request: Slack alert threading 30 6 Feature / Enhancement
#1188 Add basic arithmetic functions to templating funcmap 27 19 Feature / Enhancement
#2120 Feature suggestion: Add Gotify as receiver 26 10 Feature / Enhancement
#3729 Feature suggestion: Add Apprise library to support more notification services 25 4 Feature / Enhancement
#1196 Feature request: restrict the identity of silence creator to one passed by some HTTP header 24 27 Feature / Enhancement
#3919 Feature Request: Matrix Receiver 21 3 Feature / Enhancement

Triage Findings

Heuristic flags derived from issue body text, labels and age. Each entry needs human confirmation before acting.

Likely Already Fixed (1)

Issue body references a merge/fix that may already be released:

Potentially Invalid / No Longer Valid (13)

Candidates to close as not-a-bug, by-design, abandoned or obsolete:

Potential Duplicate / Overlapping Clusters (16)

Issues grouped by recurring theme — strong candidates for consolidation into a single tracking issue:

Templating helper / function requests (21)

Spurious / extra 'resolved' notifications (17)

Requests for new notification integrations (15)

Inhibition rule expressiveness (12)

Duplicate / repeated notifications in HA (10)

Slack threading / attachments / blocks (9)

OpsGenie / JSM behaviour (8)

Config auto-reload / reload behaviour (7)

Jira integration (6)

repeat_interval timing complaints (6)

IPv6 / hostname binding & advertise-address (5)

Silence creator/comment handling (4)

Pagination of alerts/silences/groups API (4)

Expired silences not garbage-collected (4)

'dropping messages because too many are queued' (3)

MSTeams adaptive cards / actions (3)

Blocked: Waiting for Reporter (14)

Tagged kind/more-info-needed / waiting-for-user-input:

Stale: No Activity > 1 Year (142)

Sorted by staleness (most stale first):

Full Issue Listing by Category

Bug (23)

Documentation (15)

Cleanup / Tech-debt (2)

Feature / Enhancement (157)

Question (11)

Support (25)

Change / Proposal (1)

Friction (1)

Release / Packaging (1)

Uncategorized (91)

Appendix: Label Distribution

Label Count
stale 114
kind/enhancement 105
component/notify 68
help wanted 35
component/ui 31
kind/support 26
component/config 18
component/silences 17
component/api 14
kind/documentation 12
component/high availability 12
kind/more-info-needed 12
component/templating 12
kind/bug 10
keepalive 9
kind/question 9
component/inhibition 4
discuss-in-meeting 3
component/cli 3
component/storage 3
kind/friction 2
component/dispatch 2
waiting-for-user-input 2
kind/cleanup 2
component/nflog 2
kind/release 1
kind/change 1
hacktoberfest 1

Methodology & Caveats

  • Data pulled live from the GitHub REST API (state=open); pull requests are excluded.
  • Categories are assigned from kind/* labels first, falling back to title-keyword inference only when no kind/* label exists.
  • Fixed / invalid flags are keyword heuristics over the issue body (not comments) and will contain false positives — treat as a triage shortlist, not a verdict.
  • Duplicate clusters are thematic groupings by title regex; members are related, not necessarily exact duplicates.
  • Stale = no update in >365 days.

Metadata

Metadata

Assignees

Labels

keepaliveExempt from stale checks

Type

No type
No fields configured for issues without a type.

Projects

Status
To triage

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions