Is Dynatrace down?

We are investigating an issue affecting access to the Platform BizEvents (Business Events) settings page in customer environments. As a result, some customers may be unable to create, modify, or disable BizEvents through the affected settings page: /ui/apps/dynatrace.settings/settings/bizevents. BizEvent processing is uninterrupted at this time.  Our teams are actively working to restore access and minimize customer impact. We apologize for the disruption and will provide additional updates as more information becomes available.

We have identified an issue that may prevent some customers from deploying Operator 1.10.1 on fresh deployments or upgrades where operator components have been deleted. In some cases, this may delay planned changes in production environments While we work toward a resolution, we have published a Community post with workaround guidance for impacted customers. Please refer to our Community post: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Unable-to-deploy-Operator-1-10-1-on-fresh-clusters-or-upgrades/ta-p/302391 We apologize for the inconvenience and appreciate your patience as we work to restore normal deployment functionality.

We are currently experiencing a technical issue that may delay our ability to view updates submitted through our Customer Support Portal, including support cases, licensing requests, and other inquiries. Our team is actively working to resolve this as quickly as possible. If you have an urgent matter, please reach out to us directly via Dynatrace chat support so we can ensure your request is seen and addressed without delay. We appreciate your patience and will provide an update as soon as normal service is restored.

We have identified a potential issue affecting OpenShift observability when upgrading to OA 1.341. This may result in reduced or lost visibility into OpenShift environments, which could impact monitoring of production environments. Our team is aware of the issue and is actively working on a fix. We recommend that customers review this potential impact before proceeding with the upgrade and continue monitoring their OpenShift environments closely. If you have already upgraded to OA 1.341, please open up a support case so that our team can assist with reverting you back to the previous version, which is not affected by this issue.

Our team continues to actively work on a fix. In the meantime, we have published a community article with downgrade instructions to assist customers who may be affected by the OpenShift monitoring issue after upgrading to OneAgent version 1.341: https://community.dynatrace.com/t5/Troubleshooting/k8s-oc-Downgrading-OneAgent-in-Kubernetes-and-OpenShift-with-the/ta-p/302087 If you require assistance with the downgrade process, please open a support case and our team will assist you accordingly. We apologise for any inconvenience this issue may cause.

We have narrowed the scope of the issue and customers using application-only monitoring are not expected to be affected.​‌ While we continue to work on a fix, customers experiencing this issue can use the previously provided downgrade guidance or contact Dynatrace Support for assistance.​‌ We will provide further updates as they become available. We apologize for any inconvenience this issue may cause.

We have identified an issue in OneAgent .NET version 1.341 affecting IBM MQ tracing. In impacted environments, IBM MQ message processing may be disrupted, which can affect applications consuming IBM MQ messages. Our engineering teams have identified the root cause and are actively working on a fix to resolve this issue. A workaround is available for customers currently experiencing this issue. Customers requiring assistance are encouraged to open a Support case with Dynatrace for guidance. Further updates will be provided as progress is made. We apologize for the inconvenience and appreciate your patience and understanding as we work to resolve this issue