<?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 Avoiding host unavailable alerts for GCP preemptible VMs? in Container platforms</title>
    <link>https://community.dynatrace.com/t5/Container-platforms/Avoiding-host-unavailable-alerts-for-GCP-preemptible-VMs/m-p/118215#M494</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I was wondering if anyone has worked with &lt;A rel="noopener noreferrer nofollow" href="https://cloud.google.com/preemptible-vms/" target="_blank"&gt;Googles Preemptible&lt;/A&gt; nodes. These are basically discounted resources that have a max lifespan of 24hours bur can be terminated at any time.&lt;/P&gt;&lt;P&gt;This is quite useful to use with GKE (K8s) as K8s takes care of rescheduling workloads.&lt;/P&gt;&lt;P&gt;However when using with Dynatrace when these hosts get killed they will create host unavailable alerts.&lt;BR /&gt;In the case of a K8s cluster this should be handled differently and not alerted.&lt;/P&gt;&lt;P&gt;First I thought of just creating a customized anomaly detection based on tagging these preemptible nodes, but that is not possible in Dynatrace.&lt;BR /&gt;Then I thought of creating an alerting profile that &lt;STRONG&gt;excludes&lt;/STRONG&gt; these tagged hosts but that is also not possible (see here: &lt;A rel="noopener noreferrer" href="https://community.dynatrace.com/idea/241247/view.html" target="_blank"&gt;https://community.dynatrace.com/idea/241247/view.html&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;Then I looked a bit deeper into Google's documentation and found that when a preemptible node is being shut down GCP sends a ACPI G2 Soft Off signal that should be captured by a user script to ensure a graceful shutdown of the services running on a preemptible host.&lt;/P&gt;&lt;P&gt;For me this seems to be the logical step, let the Dyantrace agent detect this G2 Soft Off signal and react on it by performing a graceful shutdown. This would then not lead to an alert in Dynatrace. Is this something that the oneagent operator can be enhanced with?&lt;BR /&gt;I will create an RFE if no other solution exists as of yet.&lt;/P&gt;&lt;P&gt;Reinhard&lt;/P&gt;</description>
    <pubDate>Mon, 16 Oct 2023 14:17:05 GMT</pubDate>
    <dc:creator>r_weber</dc:creator>
    <dc:date>2023-10-16T14:17:05Z</dc:date>
    <item>
      <title>Avoiding host unavailable alerts for GCP preemptible VMs?</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Avoiding-host-unavailable-alerts-for-GCP-preemptible-VMs/m-p/118215#M494</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I was wondering if anyone has worked with &lt;A rel="noopener noreferrer nofollow" href="https://cloud.google.com/preemptible-vms/" target="_blank"&gt;Googles Preemptible&lt;/A&gt; nodes. These are basically discounted resources that have a max lifespan of 24hours bur can be terminated at any time.&lt;/P&gt;&lt;P&gt;This is quite useful to use with GKE (K8s) as K8s takes care of rescheduling workloads.&lt;/P&gt;&lt;P&gt;However when using with Dynatrace when these hosts get killed they will create host unavailable alerts.&lt;BR /&gt;In the case of a K8s cluster this should be handled differently and not alerted.&lt;/P&gt;&lt;P&gt;First I thought of just creating a customized anomaly detection based on tagging these preemptible nodes, but that is not possible in Dynatrace.&lt;BR /&gt;Then I thought of creating an alerting profile that &lt;STRONG&gt;excludes&lt;/STRONG&gt; these tagged hosts but that is also not possible (see here: &lt;A rel="noopener noreferrer" href="https://community.dynatrace.com/idea/241247/view.html" target="_blank"&gt;https://community.dynatrace.com/idea/241247/view.html&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;Then I looked a bit deeper into Google's documentation and found that when a preemptible node is being shut down GCP sends a ACPI G2 Soft Off signal that should be captured by a user script to ensure a graceful shutdown of the services running on a preemptible host.&lt;/P&gt;&lt;P&gt;For me this seems to be the logical step, let the Dyantrace agent detect this G2 Soft Off signal and react on it by performing a graceful shutdown. This would then not lead to an alert in Dynatrace. Is this something that the oneagent operator can be enhanced with?&lt;BR /&gt;I will create an RFE if no other solution exists as of yet.&lt;/P&gt;&lt;P&gt;Reinhard&lt;/P&gt;</description>
      <pubDate>Mon, 16 Oct 2023 14:17:05 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Avoiding-host-unavailable-alerts-for-GCP-preemptible-VMs/m-p/118215#M494</guid>
      <dc:creator>r_weber</dc:creator>
      <dc:date>2023-10-16T14:17:05Z</dc:date>
    </item>
    <item>
      <title>Re: Avoiding host unavailable alerts for GCP preemptible VMs?</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Avoiding-host-unavailable-alerts-for-GCP-preemptible-VMs/m-p/118216#M495</link>
      <description>&lt;P&gt;I'd raise this as an RFE too, but in the short term, if your script can catch the G2 Soft Off signal, you can always use this:&lt;/P&gt;
&lt;PRE&gt;POST to https://tenantID.live.dynatrace.com/api/v1/events&lt;BR /&gt;with a MARKED_FOR_TERMINATION event&lt;/PRE&gt;</description>
      <pubDate>Mon, 27 Mar 2023 07:36:37 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Avoiding-host-unavailable-alerts-for-GCP-preemptible-VMs/m-p/118216#M495</guid>
      <dc:creator>adam_gardner</dc:creator>
      <dc:date>2023-03-27T07:36:37Z</dc:date>
    </item>
    <item>
      <title>Re: Avoiding host unavailable alerts for GCP preemptible VMs?</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Avoiding-host-unavailable-alerts-for-GCP-preemptible-VMs/m-p/118217#M496</link>
      <description>&lt;P&gt;Not sure though what the marked for termination event would do on the problem detection AI engine then. If that ensures that the shutdown is seen as a graceful one then great - only have to ensure the DT event API is accessible.&lt;/P&gt;&lt;P&gt;I'd rather send this event to the oneagent on the host directly instead of the tenant event API.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Oct 2020 14:03:59 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Avoiding-host-unavailable-alerts-for-GCP-preemptible-VMs/m-p/118217#M496</guid>
      <dc:creator>r_weber</dc:creator>
      <dc:date>2020-10-27T14:03:59Z</dc:date>
    </item>
    <item>
      <title>Re: Avoiding host unavailable alerts for GCP preemptible VMs?</title>
      <link>https://community.dynatrace.com/t5/Container-platforms/Avoiding-host-unavailable-alerts-for-GCP-preemptible-VMs/m-p/118218#M497</link>
      <description>Yeah, that's the idea, avoid raising a problem for that host.&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;In my old org was used when sending a termination for short life cycle EC2 instances and a lambda executed the calls to the API in such events.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Oct 2020 16:15:01 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Container-platforms/Avoiding-host-unavailable-alerts-for-GCP-preemptible-VMs/m-p/118218#M497</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-10-27T16:15:01Z</dc:date>
    </item>
  </channel>
</rss>

