Grafana bot for Lark
Grafana dashboards are for observation, not for hoping someone checks them. The Grafana bot sends alert firing, recovery and key panel snapshots to Lark, so the team gets metric context when the alert arrives.
What it solves
- Alerts stay in Grafana and the responder sees them late.
- Without recovery notices, the team does not know when the issue is over.
- Alert messages lack dashboard context, so investigation starts with a tab hunt.
Core capabilities
Firing and recovery
Grafana alert state changes include the rule, severity and current status.
Panel snapshots
Attach key panel snapshots to the alert so investigation needs fewer jumps.
Team subscriptions
Route alerts to the group that owns the service or team.
Severity routing
Decide which severities notify, where they go and whether they escalate.
How to connect
- Add the bot to the Lark group and get its webhook URL.
- Configure the event source, target group and notification rules.
- Send a test event and confirm the message and @mention.
This page does not show the internal console. Configuration details and permissions are provided during onboarding, or contact sales to learn more.
Who it is for
- SRE and operations
- Engineering teams
- Platform engineering
FAQ
Does it support Grafana Cloud?
Yes. It connects through Grafana alert webhooks, so both Cloud and self-managed instances can be configured.
Do panel snapshots require extra permissions?
Snapshot behavior depends on your Grafana configuration and permissions.
Related capabilities and solutions
Bring this capability into your Lark groups
Tell us about your team and use case. We will recommend SaaS or self-hosted deployment.