feat(grafana-oncall): enrich notification payload with monitor details, tags and type-specific fields#263
Open
brewle wants to merge 1 commit into0xfurai:mainfrom
Open
Conversation
…e-specific fields
✅ Deploy Preview for peekaping ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for docspeekaping ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The existing Grafana OnCall provider sent minimal payload with only
title,messageandstate, making it impossible to build meaningful alert grouping and routing in Grafana OnCall.Changes
1.
shared/monitor.model.goAdded
Tags []stringfield toMonitormodel to make monitor tags available across the codebase.2.
monitor/monitor.sql.repository.goExtended
FindByIDto load tag names via a second query joiningmonitor_tagsandtagstables.3.
notification_channel/providers/grafana_oncall.goEnriched payload with:
status,ping_ms,retries,time,monitor_id,monitor_type,tagshttp,http-keyword,http-json-query):monitor_url,http_status_codetcp,ping,dns,grpc-keyword):monitor_hostmysql,postgres,redis, etc.): base payload only – DSN may contain credentialsExample payloads
Alert:
{ "title": "example.com is down", "message": "HTTP request failed with status: 503", "state": "alerting", "status": "DOWN", "ping_ms": 685, "retries": 2, "time": "2026-02-27T00:21:00Z", "http_status_code": "503", "monitor_id": "3215c0fd-...", "monitor_type": "http", "monitor_url": "https://example.com", "tags": ["severity:critical", "country:ua"] }Resolve:
{ "title": "example.com is up", "message": "200 - 200 OK", "state": "ok", "status": "UP", "ping_ms": 167, "retries": 0, "time": "2026-02-27T00:25:00Z", "http_status_code": "200", "monitor_id": "3215c0fd-...", "monitor_type": "http", "monitor_url": "https://example.com", "tags": ["severity:critical", "country:ua"] }