Sentry bot for Lark
Sentry finds the error, but someone still has to see it. The Sentry bot sends new issues, error trends and alert-rule triggers to the right Lark group, so the responder and feature owner can decide what to do in one place.
What it solves
- New issues stay in Sentry and the team hears about them late.
- Alert-rule triggers arrive without a clear owner or context.
- Error trends are only noticed when someone opens the dashboard.
Core capabilities
New issue alerts
New issues, regressions and key errors are posted per project.
Alert rules
Sentry alert triggers and resolutions include project, environment and severity context.
Severity filters
Only receive issues above the severity you choose.
On-call handoff
Pair with the on-call bot to escalate urgent alerts to the current responder.
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
- Engineering teams
- SRE and operations
- Leaders responsible for production reliability
FAQ
Can each project target a different group?
Yes. Each Sentry project can have its own Lark group and notification scope.
Are recovery events included?
Yes. Both trigger and recovery events can be sent based on your configuration.
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.