<?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: update problem closure email notification in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Update-quot-Problem-closure-quot-email-notification/m-p/285849#M5884</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I would say checking out-the-box placeholders "{XXX}" available in email integration.&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
    <pubDate>Fri, 12 Sep 2025 06:54:39 GMT</pubDate>
    <dc:creator>AntonPineiro</dc:creator>
    <dc:date>2025-09-12T06:54:39Z</dc:date>
    <item>
      <title>Update "Problem closure" email notification</title>
      <link>https://community.dynatrace.com/t5/Alerting/Update-quot-Problem-closure-quot-email-notification/m-p/285845#M5880</link>
      <description>&lt;P&gt;currently , email notification body is updated with event.description field in Davis Anamoly Detector app , i want to have a different email body incase of the issue closure - example : Alert condition is solved , how can i configure it&lt;/P&gt;</description>
      <pubDate>Thu, 18 Dec 2025 12:11:42 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Update-quot-Problem-closure-quot-email-notification/m-p/285845#M5880</guid>
      <dc:creator>O11y_Noob</dc:creator>
      <dc:date>2025-12-18T12:11:42Z</dc:date>
    </item>
    <item>
      <title>Re: update problem closure email notification</title>
      <link>https://community.dynatrace.com/t5/Alerting/Update-quot-Problem-closure-quot-email-notification/m-p/285849#M5884</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I would say checking out-the-box placeholders "{XXX}" available in email integration.&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Fri, 12 Sep 2025 06:54:39 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Update-quot-Problem-closure-quot-email-notification/m-p/285849#M5884</guid>
      <dc:creator>AntonPineiro</dc:creator>
      <dc:date>2025-09-12T06:54:39Z</dc:date>
    </item>
    <item>
      <title>Re: update problem closure email notification</title>
      <link>https://community.dynatrace.com/t5/Alerting/Update-quot-Problem-closure-quot-email-notification/m-p/285899#M5885</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;unfortunately, it’s not possible to configure a separate message for "Send email if problem closed."&lt;/P&gt;&lt;P&gt;I suggest using:&lt;BR /&gt;{State}: Problem state. Possible values are OPEN or RESOLVED.&lt;/P&gt;&lt;P&gt;The list of placeholders is below:&lt;/P&gt;&lt;H4&gt;Available placeholders&lt;/H4&gt;&lt;P&gt;&lt;STRONG&gt;{ImpactedEntities}&lt;/STRONG&gt;: Details about the entities impacted by the problem in form of a json array.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{ImpactedEntity}&lt;/STRONG&gt;: A short description of the problem and impacted entity (or multiple impacted entities).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{ImpactedEntityNames}&lt;/STRONG&gt;: The entity impacted by the problem.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{NamesOfImpactedEntities}&lt;/STRONG&gt;: The names of all entities that are impacted by the problem.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{PID}&lt;/STRONG&gt;: Unique system identifier of the reported problem.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{ProblemDetailsHTML}&lt;/STRONG&gt;: All problem event details including root cause as an HTML-formatted string.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{ProblemDetailsJSONv2}&lt;/STRONG&gt;: Problem as json object following the structure from the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="" href="https://dt-url.net/7a03ti2" target="_blank" rel="noopener"&gt;Dynatrace Problems V2 API&lt;/A&gt;. The optional fields evidenceDetails and impactAnalysis are included, but recentComments is not.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{ProblemDetailsJSON}&lt;/STRONG&gt;: Problem as json object following the structure from the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A class="" href="https://dt-url.net/qn23tk2" target="_blank" rel="noopener"&gt;Dynatrace Problems V1 API&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{ProblemDetailsMarkdown}&lt;/STRONG&gt;: All problem event details including root cause as a Markdown-formatted string.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{ProblemDetailsText}&lt;/STRONG&gt;: All problem event details including root cause as a text-formatted string.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{ProblemID}&lt;/STRONG&gt;: Display number of the reported problem.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{ProblemImpact}&lt;/STRONG&gt;: Impact level of the problem. Possible values are APPLICATION, SERVICE, or INFRASTRUCTURE.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{ProblemSeverity}&lt;/STRONG&gt;: Severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, or CUSTOM_ALERT.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{ProblemTitle}&lt;/STRONG&gt;: Short description of the problem.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{ProblemURL}&lt;/STRONG&gt;: URL of the problem within Dynatrace.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{State}&lt;/STRONG&gt;: Problem state. Possible values are OPEN or RESOLVED.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;{Tags}&lt;/STRONG&gt;: Comma separated list of tags that are defined for all impacted entities. To refer to the value of a specific tag, specify the tag's key in square brackets:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;{Tags[key]}&lt;/STRONG&gt;. If the tag does not have any assigned value, the placeholder will be replaced by an empty string. The placeholder will not be replaced if the tag key does not exist.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Sep 2025 14:51:25 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Update-quot-Problem-closure-quot-email-notification/m-p/285899#M5885</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2025-09-12T14:51:25Z</dc:date>
    </item>
  </channel>
</rss>

