Live

Host and Process Availability Monitoring Issue on Managed Version 1.350

Partial outageOfficial update
0

Host and process availability monitoring does not work on Dynatrace Managed clusters that run version 1.350, and availability alerts may not occur. Dynatrace reports that the issue is under investigation. A workaround is available with assistance from Dynatrace Support.

State

Investigating

Started

Ongoing for

48 min

Worst impact

Partial outage

Timeline

1 update
12:0112:1312:2512:3712:49
Partial outageUpdate postedTimes in UTC

Investigating

48 min 100%

Updates

Times in UTC

As posted by Dynatrace

Investigating

We have identified an issue affecting Dynatrace Managed clusters running version 1.350, where availability events may not be generated when monitored hosts or processes become unavailable. As a result, customers may not receive the expected alerts when a monitored host or process becomes unavailable. Our teams are actively working on a fix. A workaround is available and can be applied with assistance from Dynatrace Support. If you would like to proceed with the workaround, please contact Dynatrace Support for assistance. We will provide our next update within four hours, or sooner if further information becomes available.

Affected components

2
Dynatrace ecosystem servicesDynatrace Managed

Dynatrace in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

4

Median duration

7 h 8 min

This incident

89% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

31 h 7 min
median 7 h 8 min
90 days agoToday

Other Dynatrace incidents

All incidents

Follow Dynatrace

Your coding agent knows when Dynatrace is down, and tells you when a failure is theirs, not yours. You can also get Dynatrace incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "dynatrace" and tell me if Dynatrace has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=dynatrace
Slack
/feed subscribe https://outages.live/feed.xml?providers=dynatrace

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane