Escalate application health violations fast
Every few minutes, WebRun opens AppDynamics, checks for newly triggered health rule violations like a response time or error rate breach, posts the details to the team's Telegram channel, and texts the on call engineer through Twilio when the violation is marked critical severity so a real production problem is never left waiting behind routine noise.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I escalate critical AppDynamics health rule violations to on call?
WebRun checks AppDynamics every few minutes for newly triggered health rule violations such as a response time or error rate breach. It posts every violation to Telegram for the team, and texts the on call engineer through Twilio when the severity is critical, so a real production problem never waits behind routine noise.
- Critical severity violations reach on call within minutes
- Every violation is visible in Telegram, not just the critical ones
- Routine violations stop competing for on call attention
Built for SRE teams · application support teams · platform engineers · DevOps
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
login.appdynamics.comin a real browser with your saved login - no setup, no API keys. -
1
AppDynamics - check for triggered health rule violations
WebRun opens AppDynamics to check for triggered health rule violations. - Open AppDynamics and check for health rule violations triggered since the last run
- Capture the application, the rule that triggered, and the severity
- Skip violations already alerted on
Done when Every newly triggered violation is listed with its application and severity.
-
2
Telegram - post the violation to the team
WebRun opens Telegram to post the violation to the team. - Post each newly triggered violation to the team channel
- Show the application, the rule, and the severity
- Note which ones are also being escalated to on call
Done when The team channel has an entry for every newly triggered violation.
-
3
Twilio - page on call for critical severity
WebRun opens Twilio to page on call for critical severity. - Text the on call engineer only for violations marked critical severity
- Name the application and the rule that triggered
- Skip the text for anything below critical severity
Done when The on call engineer has a text for every critical severity violation.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it restart the application or change any health rules?
No. WebRun only reports what AppDynamics already flagged. Restarting a service or changing a rule is always done by your engineers.
What decides critical severity?
The severity AppDynamics already assigns to the health rule violation. WebRun does not reclassify it.
Why text only for critical ones?
So the on call engineer's phone isn't used for routine violations. Everything still posts to Telegram for full visibility.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.