grafana-util alert set-route
What this page covers
Author or replace the tool-owned staged notification route.
When to open this page
- Replace the managed route with a new receiver and matcher set.
- Re-run the command to fully replace the managed route instead of merging fields.
Who this page is for
Best for operators who review alert rules, routes, contact points, and staged alert changes.
Purpose
Author or replace the tool-owned staged notification route.
When to use
- Replace the managed route with a new receiver and matcher set.
- Re-run the command to fully replace the managed route instead of merging fields.
Key flags
--desired-dirpoints to the staged alert tree.--receiversets the route receiver.--labeladds route matchers inkey=valueform.--severityadds a convenience severity matcher.--dry-runrenders the managed route document without writing files.
Before / After
- Before: edit the managed route tree by hand and keep the matcher shape in your head.
- After: write one staged route document that encodes the receiver and matcher set you want.
What success looks like
- The staged route tree contains the receiver and matcher values you intended.
- A dry-run shows the route document you would write before touching files.
- The route is easy to compare against
preview-routeoutput.
Failure checks
- Check that
--desired-dirpoints at the correct staged tree before overwriting anything. - Verify the receiver and matcher labels before trusting the generated route.
- If the dry-run does not match the intended route, stop and correct the matcher set first.
Examples
# Purpose: Author or replace the tool-owned staged notification route.
grafana-util alert set-route --desired-dir ./alerts/desired --receiver pagerduty-primary --label team=platform --severity critical# Purpose: Author or replace the tool-owned staged notification route.
grafana-util alert set-route --desired-dir ./alerts/desired --receiver pagerduty-primary --label team=platform --severity critical --dry-run