Dynatrace-Azure Automation Webhook Setup
Budget: ₹37,500 – ₹75,000 INR
Need daily support -2hrs maximum
I need a clean, reliable link between Dynatrace and Azure Automation so that production incidents resolve themselves before users ever notice.
Here is what must happen:
• Whenever Dynatrace detects a hung server, a webhook should fire that calls an Azure Automation runbook to restart the affected JVM.
• The same workflow must also push an alert/notification to our existing channel (Teams or email—whichever you wire first) and execute a short diagnostic script so we keep a snapshot of the state that caused the hang.
You are free to script the runbook in PowerShell or Python, but the solution has to:
• Be deployable through native Azure Automation assets (no extra servers or agents).
• Map webhook payloads cleanly to the runbook parameters so operators can see which host was acted on.
• Return success/error status back to Dynatrace for proper timeline tracking.
I will test by putting a node into a simulated hung state; the job must restart that JVM, confirm it is back up, and send the log + notification automatically. Once that passes in both staging and prod subscriptions, we are done.
If you have already linked Dynatrace with Azure Automation on previous projects, this should be straightforward and quick.
I need a clean, reliable link between Dynatrace and Azure Automation so that production incidents resolve themselves before users ever notice.
Here is what must happen:
• Whenever Dynatrace detects a hung server, a webhook should fire that calls an Azure Automation runbook to restart the affected JVM.
• The same workflow must also push an alert/notification to our existing channel (Teams or email—whichever you wire first) and execute a short diagnostic script so we keep a snapshot of the state that caused the hang.
You are free to script the runbook in PowerShell or Python, but the solution has to:
• Be deployable through native Azure Automation assets (no extra servers or agents).
• Map webhook payloads cleanly to the runbook parameters so operators can see which host was acted on.
• Return success/error status back to Dynatrace for proper timeline tracking.
I will test by putting a node into a simulated hung state; the job must restart that JVM, confirm it is back up, and send the log + notification automatically. Once that passes in both staging and prod subscriptions, we are done.
If you have already linked Dynatrace with Azure Automation on previous projects, this should be straightforward and quick.