<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Host or Monitoring Unavailable in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Host-or-Monitoring-Unavailable/m-p/125964#M2000</link>
    <description>&lt;DIV class="fr-view clearfix"&gt;&lt;P&gt;@Tarun A. Without being fully aware of your process for autoscaling, I would propose a few ideas. If these devices are defined and chosen prior to the autoscaling action, setup an automatic tag to tag them and have a maintenance window that is set off of that defined tag. That would suppress these alarms. &lt;/P&gt;&lt;P&gt;OR&lt;/P&gt;&lt;P&gt;Within the Alert profile page, select the alert profile and exclude the hosts slated for autoscaling to be excluded from alerts. &lt;/P&gt;&lt;P&gt;OR &lt;/P&gt;&lt;P&gt;Globally, change your settings to not alert on graceful shutdowns and have your hosts shutdown gracefully. This will then not alert you when the host is shutdown. You can also go into the settings page and disable the one agent on the host prior to the auto scaling. &lt;/P&gt;&lt;P&gt; &lt;IMG src="https://community.dynatrace.com/legacyfs/online/22894-graceful-shutdown.png" /&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/22895-monitoring-overview.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thank you, &lt;/P&gt;&lt;P&gt;Chad&lt;/P&gt;&lt;BR /&gt;&lt;/DIV&gt;</description>
    <pubDate>Thu, 12 Dec 2019 13:50:54 GMT</pubDate>
    <dc:creator>ctturner</dc:creator>
    <dc:date>2019-12-12T13:50:54Z</dc:date>
    <item>
      <title>Host or Monitoring Unavailable</title>
      <link>https://community.dynatrace.com/t5/Alerting/Host-or-Monitoring-Unavailable/m-p/125961#M1997</link>
      <description>&lt;P&gt;We are doing autoscaling and  whenever we scale down instances we are receiving host or monitoring unavailable alert and we don't that alert to be triggered in this scenario.Can you please help us how can we disable alert.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Dec 2019 01:40:17 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Host-or-Monitoring-Unavailable/m-p/125961#M1997</guid>
      <dc:creator>tarun_kumar_aga</dc:creator>
      <dc:date>2019-12-12T01:40:17Z</dc:date>
    </item>
    <item>
      <title>Re: Host or Monitoring Unavailable</title>
      <link>https://community.dynatrace.com/t5/Alerting/Host-or-Monitoring-Unavailable/m-p/125962#M1998</link>
      <description>&lt;P&gt;Only way I have in mind is maintenance window. During scaling down, you can send request to DT to fire up maintenance window that will cover those hosts that will be disconnected. Than do scaling down, after few minutes disable maintenance window. This is really dirty workaround but I don't have other idea for now.&lt;/P&gt;&lt;P&gt;Sebastian &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Dec 2019 07:52:13 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Host-or-Monitoring-Unavailable/m-p/125962#M1998</guid>
      <dc:creator>skrystosik</dc:creator>
      <dc:date>2019-12-12T07:52:13Z</dc:date>
    </item>
    <item>
      <title>Re: Host or Monitoring Unavailable</title>
      <link>https://community.dynatrace.com/t5/Alerting/Host-or-Monitoring-Unavailable/m-p/125963#M1999</link>
      <description>&lt;P&gt;How exactly are you "descaling" your environment? Probably the best approach would be to uninstall the agents before shutting down the instances. Then you would not get the problems about unavailable hosts.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Dec 2019 09:53:59 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Host-or-Monitoring-Unavailable/m-p/125963#M1999</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2019-12-12T09:53:59Z</dc:date>
    </item>
    <item>
      <title>Re: Host or Monitoring Unavailable</title>
      <link>https://community.dynatrace.com/t5/Alerting/Host-or-Monitoring-Unavailable/m-p/125964#M2000</link>
      <description>&lt;DIV class="fr-view clearfix"&gt;&lt;P&gt;@Tarun A. Without being fully aware of your process for autoscaling, I would propose a few ideas. If these devices are defined and chosen prior to the autoscaling action, setup an automatic tag to tag them and have a maintenance window that is set off of that defined tag. That would suppress these alarms. &lt;/P&gt;&lt;P&gt;OR&lt;/P&gt;&lt;P&gt;Within the Alert profile page, select the alert profile and exclude the hosts slated for autoscaling to be excluded from alerts. &lt;/P&gt;&lt;P&gt;OR &lt;/P&gt;&lt;P&gt;Globally, change your settings to not alert on graceful shutdowns and have your hosts shutdown gracefully. This will then not alert you when the host is shutdown. You can also go into the settings page and disable the one agent on the host prior to the auto scaling. &lt;/P&gt;&lt;P&gt; &lt;IMG src="https://community.dynatrace.com/legacyfs/online/22894-graceful-shutdown.png" /&gt;&lt;IMG src="https://community.dynatrace.com/legacyfs/online/22895-monitoring-overview.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thank you, &lt;/P&gt;&lt;P&gt;Chad&lt;/P&gt;&lt;BR /&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 12 Dec 2019 13:50:54 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Host-or-Monitoring-Unavailable/m-p/125964#M2000</guid>
      <dc:creator>ctturner</dc:creator>
      <dc:date>2019-12-12T13:50:54Z</dc:date>
    </item>
    <item>
      <title>Re: Host or Monitoring Unavailable</title>
      <link>https://community.dynatrace.com/t5/Alerting/Host-or-Monitoring-Unavailable/m-p/180742#M2857</link>
      <description>&lt;P&gt;There is now the option to post a 'marked for termination' event via the Events API.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.dynatrace.com/support/help/shortlink/event-types-info#marked-for-termination" target="_blank"&gt;https://www.dynatrace.com/support/help/shortlink/event-types-info#marked-for-termination&lt;/A&gt;&lt;A href="https://www.dynatrace.com/support/help/shortlink/api-events-v2-post-event" target="_blank"&gt;&amp;nbsp;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.dynatrace.com/support/help/shortlink/api-events-v2-post-event" target="_blank"&gt;https://www.dynatrace.com/support/help/shortlink/api-events-v2-post-event&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 08:09:29 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Host-or-Monitoring-Unavailable/m-p/180742#M2857</guid>
      <dc:creator>andre_vdveen</dc:creator>
      <dc:date>2022-02-15T08:09:29Z</dc:date>
    </item>
  </channel>
</rss>

