<?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: Problem integrations - Emails - Show problem &amp;quot;startTime&amp;quot; variable in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-integrations-Emails-Show-problem-quot-startTime-quot/m-p/294144#M4654</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;In Dynatrace Managed classic Problem notifications → Email, you can only use the placeholders shown under “Available placeholders” in the UI.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Available placeholders
{ImpactedEntities}: Details about the entities impacted by the problem in form of a json array.

{ImpactedEntity}: A short description of the problem and impacted entity (or multiple impacted entities).

{ImpactedEntityNames}: The entity impacted by the problem.

{NamesOfImpactedEntities}: The names of all entities that are impacted by the problem.

{PID}: Unique system identifier of the reported problem.

{ProblemDetailsHTML}: All problem event details including root cause as an HTML-formatted string.

{ProblemDetailsJSONv2}: Problem as json object following the structure from the Dynatrace Problems V2 API. The optional fields evidenceDetails and impactAnalysis are included, but recentComments is not.

{ProblemDetailsJSON}: Problem as json object following the structure from the Dynatrace Problems V1 API.

{ProblemDetailsMarkdown}: All problem event details including root cause as a Markdown-formatted string.

{ProblemDetailsText}: All problem event details including root cause as a text-formatted string.

{ProblemID}: Display number of the reported problem.

{ProblemImpact}: Impact level of the problem. Possible values are APPLICATION, SERVICE, or INFRASTRUCTURE.

{ProblemSeverity}: Severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, or CUSTOM_ALERT.

{ProblemTitle}: Short description of the problem.

{ProblemURL}: URL of the problem within Dynatrace.

{State}: Problem state. Possible values are OPEN or RESOLVED.

{Tags}: 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: {Tags[key]}. 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;/LI-CODE&gt;&lt;P&gt;there’s no {StartTime} / {ProblemStartTime} placeholder, then you can’t extract a single field (like startTime) from {ProblemDetailsJSONv2} inside the email template—Dynatrace does not support referencing sub-elements of the JSON in notification configuration.&lt;BR /&gt;&lt;BR /&gt;The only workaround IMO is do it on reciving side, I mean use a webhook / custom integration and send {ProblemDetailsJSONv2}, then parse it on the receiving side and generate your own email containing only startTime, etc.&lt;BR /&gt;Or&amp;nbsp;in some automation, call Problems API v2 to fetch problem details (includes startTime) and then compose the email.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/problems-v2/problems/get-problem-details" target="_self"&gt;Problems API v2&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Feb 2026 12:13:42 GMT</pubDate>
    <dc:creator>t_pawlak</dc:creator>
    <dc:date>2026-02-04T12:13:42Z</dc:date>
    <item>
      <title>Problem integrations - Emails - Show problem "startTime" variable</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-integrations-Emails-Show-problem-quot-startTime-quot/m-p/294143#M4653</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In a Dynatrace Managed environment, we have email notifications sat up for problems. I wanted to show the "starttime" variable and not the whole "ProblemDetailsJSONv2" payload. Is there a way to do so?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any recommendations are appreciated.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 07:47:17 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-integrations-Emails-Show-problem-quot-startTime-quot/m-p/294143#M4653</guid>
      <dc:creator>Khalid_Alkhouli</dc:creator>
      <dc:date>2026-02-05T07:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: Problem integrations - Emails - Show problem "startTime" variable</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-integrations-Emails-Show-problem-quot-startTime-quot/m-p/294144#M4654</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;In Dynatrace Managed classic Problem notifications → Email, you can only use the placeholders shown under “Available placeholders” in the UI.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;Available placeholders
{ImpactedEntities}: Details about the entities impacted by the problem in form of a json array.

{ImpactedEntity}: A short description of the problem and impacted entity (or multiple impacted entities).

{ImpactedEntityNames}: The entity impacted by the problem.

{NamesOfImpactedEntities}: The names of all entities that are impacted by the problem.

{PID}: Unique system identifier of the reported problem.

{ProblemDetailsHTML}: All problem event details including root cause as an HTML-formatted string.

{ProblemDetailsJSONv2}: Problem as json object following the structure from the Dynatrace Problems V2 API. The optional fields evidenceDetails and impactAnalysis are included, but recentComments is not.

{ProblemDetailsJSON}: Problem as json object following the structure from the Dynatrace Problems V1 API.

{ProblemDetailsMarkdown}: All problem event details including root cause as a Markdown-formatted string.

{ProblemDetailsText}: All problem event details including root cause as a text-formatted string.

{ProblemID}: Display number of the reported problem.

{ProblemImpact}: Impact level of the problem. Possible values are APPLICATION, SERVICE, or INFRASTRUCTURE.

{ProblemSeverity}: Severity level of the problem. Possible values are AVAILABILITY, ERROR, PERFORMANCE, RESOURCE_CONTENTION, or CUSTOM_ALERT.

{ProblemTitle}: Short description of the problem.

{ProblemURL}: URL of the problem within Dynatrace.

{State}: Problem state. Possible values are OPEN or RESOLVED.

{Tags}: 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: {Tags[key]}. 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;/LI-CODE&gt;&lt;P&gt;there’s no {StartTime} / {ProblemStartTime} placeholder, then you can’t extract a single field (like startTime) from {ProblemDetailsJSONv2} inside the email template—Dynatrace does not support referencing sub-elements of the JSON in notification configuration.&lt;BR /&gt;&lt;BR /&gt;The only workaround IMO is do it on reciving side, I mean use a webhook / custom integration and send {ProblemDetailsJSONv2}, then parse it on the receiving side and generate your own email containing only startTime, etc.&lt;BR /&gt;Or&amp;nbsp;in some automation, call Problems API v2 to fetch problem details (includes startTime) and then compose the email.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.dynatrace.com/docs/dynatrace-api/environment-api/problems-v2/problems/get-problem-details" target="_self"&gt;Problems API v2&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2026 12:13:42 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Problem-integrations-Emails-Show-problem-quot-startTime-quot/m-p/294144#M4654</guid>
      <dc:creator>t_pawlak</dc:creator>
      <dc:date>2026-02-04T12:13:42Z</dc:date>
    </item>
  </channel>
</rss>

