<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Troubleshoot monitoring interruptions | Dynatrace help</title>
    <description></description>
    <link>https://www.dynatrace.com/support/help/</link>
    <atom:link href="https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/troubleshooting/troubleshoot-monitoring-interruptions/feed.xml" rel="self" type="application/rss+xml"/>
    <lastBuildDate>Fri, 18 Oct 2019 07:17:18 +0200</lastBuildDate>
    <pubDate>Mon, 08 Apr 2019 13:05:46 +0200</pubDate>
    <generator>Metalsmith v2.3.0</generator>
    <item>
      <title>Troubleshoot monitoring interruptions updated on Mon, 08 Apr 2019 13:05:46 +0200</title>
      <description>&lt;p&gt;A monitoring interruption is a situation where the majority of your installed OneAgents lose their connection with the Dynatrace server and usually manifests itself as a lack of visibility in terms of both availability and performance monitoring.&lt;/p&gt;
&lt;p&gt;This doesn&amp;apos;t necessarily mean an outage of your servers though. In case of a monitoring interruption, Dynatrace automatically suppresses all &lt;strong&gt;Host unavailable&lt;/strong&gt; problems and alerts you to the monitoring interruption. All hosts are set to the availability state &lt;strong&gt;Unmonitored&lt;/strong&gt; for the duration of the monitoring outage. Monitoring interruption alerts do have a special severity filter within your alerting profiles. The &lt;code&gt;Monitoring unavailable alert&lt;/code&gt; severity level allows you to create a filter and then deliver these highly critical alerts to your monitoring operations teams.&lt;/p&gt;
&lt;p&gt;Monitoring interruptions can have different root causes depending on the type of Dynatrace deployment you&amp;apos;re running. Dynatrace SaaS environments are administered by the Dynatrace DevOps team, who post all operational issues to &lt;a href=&quot;https://dynatrace.status.io/&quot;&gt;dynatrace.status.io&lt;/a&gt;. For environments running in Dynatrace Managed deployments, it&amp;apos;s most likely that the monitoring interruption is caused by an issue within your own datacenter or network configuration.&lt;/p&gt;
&lt;p&gt;Read below for use-case specific details&lt;/p&gt;
&lt;div class=&quot;tabgroup js-tabgroup&quot; id=&quot;monitoring-interruptions&quot; data-tabgroupid=&quot;monitoring-interruptions&quot;&gt;
&lt;div class=&quot;tabs is-hidden&quot;&gt;


&lt;input class=&quot;tab__input&quot; type=&quot;radio&quot; data-target=&quot;dynatrace-saas&quot; id=&quot;monitoring-interruptions-dynatrace-saas&quot; name=&quot;monitoring-interruptions&quot; checked=&quot;checked&quot;&gt;
&lt;label class=&quot;tab&quot; for=&quot;monitoring-interruptions-dynatrace-saas&quot;&gt;Dynatrace SaaS&lt;/label&gt;


&lt;input class=&quot;tab__input&quot; type=&quot;radio&quot; data-target=&quot;dynatrace-managed&quot; id=&quot;monitoring-interruptions-dynatrace-managed&quot; name=&quot;monitoring-interruptions&quot;&gt;
&lt;label class=&quot;tab&quot; for=&quot;monitoring-interruptions-dynatrace-managed&quot;&gt;Dynatrace Managed&lt;/label&gt;

&lt;/div&gt;
&lt;div class=&quot;tabgroup__content&quot;&gt;
&lt;div class=&quot;tab__content&quot; data-content=&quot;dynatrace-saas&quot; data-title=&quot;Dynatrace SaaS&quot;&gt;
&lt;h2 id=&quot;monitoring-interruption-in-a-single-dynatrace-environment&quot;&gt;Monitoring interruption in a single Dynatrace environment
      &lt;span class=&quot;shortlink-copy shortlink-copy-js&quot; data-clipboard-text=&quot;https://www.dynatrace.com/support/help/shortlink/monitoring-interruptions#monitoring-interruption-in-a-single-dynatrace-environment&quot;&gt;
      &lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;This situation is detected whenever a single Dynatrace SaaS environment loses the connection to its OneAgents. As no other environments are affected on the same Dynatrace SaaS cluster, it&amp;apos;s highly recommended that you check the following issues within your own network configuration:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Check whether a recent change in your network or firewall configuration blocks the outgoing monitoring traffic of your OneAgents.&lt;/li&gt;
&lt;li&gt;In case you are routing OneAgent traffic through an ActiveGate, check the operational status of your ActiveGates.&lt;/li&gt;
&lt;li&gt;Finally, in case you don&amp;apos;t find any network issues within your own datacenter, check &lt;a href=&quot;https://dynatrace.status.io/&quot;&gt;dynatrace.status.io&lt;/a&gt; for a general issue in your region.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The example alert below shows a monitoring interruption within a Dynatrace SaaS environment.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://dt-cdn.net/images/environment-562-c944edfad8.png&quot; alt=&quot;monitoring interruption&quot;&gt;&lt;/p&gt;
&lt;h2 id=&quot;monitoring-interruption-within-a-dynatrace-cluster&quot;&gt;Monitoring interruption within a Dynatrace cluster
      &lt;span class=&quot;shortlink-copy shortlink-copy-js&quot; data-clipboard-text=&quot;https://www.dynatrace.com/support/help/shortlink/monitoring-interruptions#monitoring-interruption-within-a-dynatrace-cluster&quot;&gt;
      &lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;An alert is sent out to all affected monitoring environments within a Dynatrace SaaS cluster in case of a general interruption of OneAgent communication. The alert message states that the issue affects the complete Dynatrace cluster and isn&amp;apos;t limited to your own environment. As the SaaS clusters within different regions are operated by the Dynatrace DevOps team, you can check the status of your own SaaS region on &lt;a href=&quot;https://dynatrace.status.io/&quot;&gt;dynatrace.status.io&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;See below an example for an alert for a monitoring interruption on a Dynatrace SaaS region.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://dt-cdn.net/images/cluster-562-33a4cc6bc7.png&quot; alt=&quot;monitoring interruption&quot;&gt;&lt;/p&gt;

&lt;/div&gt;&lt;div class=&quot;tab__content is-hidden&quot; data-content=&quot;dynatrace-managed&quot; data-title=&quot;Dynatrace Managed&quot;&gt;
&lt;h2 id=&quot;monitoring-interruption-within-a-single-environment-within-your-a-dynatrace-managed-cluster&quot;&gt;Monitoring interruption within a single environment within your a Dynatrace Managed cluster
      &lt;span class=&quot;shortlink-copy shortlink-copy-js&quot; data-clipboard-text=&quot;https://www.dynatrace.com/support/help/shortlink/monitoring-interruptions#monitoring-interruption-within-a-single-environment-within-your-a-dynatrace-managed-cluster&quot;&gt;
      &lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;This situation is detected whenever a single environment within your Dynatrace Managed cluster loses the connection to its OneAgents. As no other environments are affected on the same Dynatrace Managed cluster, it&amp;apos;s highly recommended that you check the following issues within your own network configuration:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Check whether a recent change in your network or firewall configuration blocks the outgoing monitoring traffic of all your OneAgents.&lt;/li&gt;
&lt;li&gt;In case you&amp;apos;re routing OneAgent traffic through an ActiveGate, check the operational status of your ActiveGates.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See a typical environment monitoring interruption example below.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://dt-cdn.net/images/environment-562-c944edfad8.png&quot; alt=&quot;monitoring interruption&quot;&gt;&lt;/p&gt;
&lt;h2 id=&quot;monitoring-interruption-within-multiple-environments-on-a-dynatrace-managed-cluster&quot;&gt;Monitoring interruption within multiple environments on a Dynatrace Managed cluster
      &lt;span class=&quot;shortlink-copy shortlink-copy-js&quot; data-clipboard-text=&quot;https://www.dynatrace.com/support/help/shortlink/monitoring-interruptions#monitoring-interruption-within-multiple-environments-on-a-dynatrace-managed-cluster&quot;&gt;
      &lt;/span&gt;&lt;/h2&gt;
&lt;p&gt;An alert is sent out to all affected monitoring environments within a Dynatrace Managed cluster in case of a general interruption of OneAgent communication. The alert message states that the issue affects the complete Dynatrace Managed cluster. As the Dynatrace Managed cluster is running within your own datacenter, it&amp;apos;s recommended that you check the following possible root causes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Check the health status and cluster alerts within your Dynatrace Managed cluster management console.&lt;/li&gt;
&lt;li&gt;Identify possible network interruptions within your own datacenter.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;See an example alert for a monitoring interruption within your Dynatrace Managed cluster below.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://dt-cdn.net/images/cluster-562-33a4cc6bc7.png&quot; alt=&quot;monitoring interruption&quot;&gt;&lt;/p&gt;

&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;</description>
      <pubDate>Mon, 08 Apr 2019 13:05:46 +0200</pubDate>
      <link>https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/troubleshooting/troubleshoot-monitoring-interruptions/?updated=mon-08-apr-2019-13-05-46-0200</link>
      <guid isPermaLink="true">https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/troubleshooting/troubleshoot-monitoring-interruptions/</guid>
    </item>
  </channel>
</rss>