Best answer
Use Nerve with Grafana when a Grafana alert should reach iPhone or Android without routing sensitive operational text through chat. Grafana detects; Nerve delivers a short encrypted signal.
Where Nerve fits
Grafana is still the place for panels, alert rules, labels, history and investigation. Nerve is the phone-native delivery path for high-signal alerts. This avoids comparing Nerve to Grafana by dashboards or plugins: they solve different parts of the workflow.
Webhook pattern
Use a Grafana webhook contact point for a short payload, or run a small bridge that filters Grafana JSON and calls nerve send. Keep the phone message concise: alert name, environment, severity, dashboard URL and one useful annotation.
export NERVE_DSN="nerve://TOKEN:[email protected]"
printf 'Grafana alert: API latency high\nprod\n%s\n' "$DASHBOARD_URL" \
| nerve send --severity critical --title "Grafana alert"What not to send
Do not push raw metric dumps, full logs, secrets, customer records or noisy label sets to the phone. Link back to Grafana for investigation.
FAQ
Can the Grafana sender read old Nerve alerts?
No. A Nerve sender can create encrypted signals for one pipe. It cannot read history or decrypt previous messages.
Should every Grafana alert go to Nerve?
No. Start with page-worthy alerts only: production down, deploy broken, certificate expiring soon, backup failed, severe error budget burn.