Host and Process Availability Monitoring Issue on Managed Version 1.350
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 updateInvestigating
48 min 100%
Updates
Times in UTCAs posted by Dynatrace
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
2Dynatrace in the last 90 days
Full historyIncidents in 90 days
4
Days with an incident
4
Median duration
7 h 8 min
This incident
89% shorter than the median
Other Dynatrace incidents
All incidentsDynatrace·Metric Ingest Freshness Issue on AWS EU-WEST1 (Ireland)
Metric ingestion had delays for Dynatrace Product and Process-AWS-emea in the AWS EU-WEST1 (Ireland) region. Dynatrace reports that the incident is resolved. The incident lasted about 7 hours and 8 minutes.
Dynatrace·Support Portal Access Disruption
Dynatrace reports that the Dynatrace Support Portal and Dynatrace ecosystem services do not work for a limited number of customers. Affected users may be unable to sign in. The incident is resolved and lasted 122 minutes.
Dynatrace·Information regarding the global Microsoft 365 outage
Dynatrace reports degraded performance in parts of the Dynatrace Product and ecosystem services that rely on Microsoft. The affected components include Analyze and Automate across AWS, Azure, and GCP in the Americas, EMEA, and Asia-Pacific. Dynatrace resolved the incident after 31 hours.
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.
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.
https://outages.live/feed.xml?providers=dynatrace/feed subscribe https://outages.live/feed.xml?providers=dynatraceFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane