Skip to content

feat: implement Grafana and Glowroot alerting with Telegram and Slack support#83

Open
iambaboucarr wants to merge 2 commits into
mainfrom
feat/alerting
Open

feat: implement Grafana and Glowroot alerting with Telegram and Slack support#83
iambaboucarr wants to merge 2 commits into
mainfrom
feat/alerting

Conversation

@iambaboucarr

@iambaboucarr iambaboucarr commented Apr 7, 2026

Copy link
Copy Markdown
Collaborator
  • Added configuration options for Glowroot alerting in hosts.template and monitor.template.
  • Introduced glowroot_alerting.yml for default alerting settings.
  • Created tasks for setting up Telegram forwarder and Slack notifications in glowroot.yml.
  • Added templates for Glowroot configuration and notification policies for Grafana.
  • Implemented Prometheus alert rules and Grafana contact points for integrated alerting.
  • Enhanced Munin configuration to support Telegram and Slack alerts.

@iambaboucarr
feat: implement Grafana and Glowroot alerting with Telegram and Slack…
8a766fe 
… support

- Added configuration options for Glowroot alerting in `hosts.template` and `monitor.template`.
- Introduced `glowroot_alerting.yml` for default alerting settings.
- Created tasks for setting up Telegram forwarder and Slack notifications in `glowroot.yml`.
- Added templates for Glowroot configuration and notification policies for Grafana.
- Implemented Prometheus alert rules and Grafana contact points for integrated alerting.
- Enhanced Munin configuration to support Telegram and Slack alerts.
@iambaboucarr
docs: adding alerting documentation
de63dd8
@sonarqubecloud

sonarqubecloud Bot commented Apr 7, 2026

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
4 New issues
C Security Rating on New Code (required ≥ A)
4 New Vulnerabilities (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@iambaboucarr iambaboucarr marked this pull request as ready for review April 7, 2026 21:20
bobjolliffe
bobjolliffe reviewed May 1, 2026
View reviewed changes

@bobjolliffe bobjolliffe left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Why don't you put the alerting service into its own container? Then it doesn't have to be configured multiple times. And can be used as a generic messaging component, eg from awk scripts or whatever.

@iambaboucarr

iambaboucarr commented May 1, 2026

Copy link
Copy Markdown
Collaborator Author

Looks good. Why don't you put the alerting service into its own container? Then it doesn't have to be configured multiple times. And can be used as a generic messaging component, eg from awk scripts or whatever.

Yes, that's more scalable. Let me look into it and revert

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@bobjolliffe bobjolliffe bobjolliffe left review comments

@tkipkurgat tkipkurgat Awaiting requested review from tkipkurgat

@jason-p-pickering jason-p-pickering Awaiting requested review from jason-p-pickering

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@iambaboucarr @bobjolliffe