# Problem integrations - Emails - Show problem "startTime" variable

**URL:** <https://community.dynatrace.com/t/problem-integrations-emails-show-problem-starttime-variable/54872>\
**Category:** Dynatrace Managed\
**Tags:** integrations, dynatrace-managed, problem-notification\
**Created:** [February 4, 2026, 11:57am UTC](https://community.dynatrace.com/t/problem-integrations-emails-show-problem-starttime-variable/54872 "2026-02-04T11:57:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Khalid\_Alkhouli](https://avatars.discourse-cdn.com/v4/letter/k/eb9ed0/32.png) [@Khalid\_Alkhouli](https://community.dynatrace.com/u/Khalid_Alkhouli)\
**Post date:** [February 4, 2026, 11:57am UTC](https://community.dynatrace.com/t/problem-integrations-emails-show-problem-starttime-variable/54872/1 "2026-02-04T11:57:04Z")

</div>

Hi all,

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?

Any recommendations are appreciated.

---

<div class="post-metadata">

**Author:** ![t\_pawlak](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/t_pawlak/32/14991_2.png) [@t\_pawlak](https://community.dynatrace.com/u/t_pawlak)\
**Post date:** [February 4, 2026, 12:13pm UTC](https://community.dynatrace.com/t/problem-integrations-emails-show-problem-starttime-variable/54872/2 "2026-02-04T12:13:42Z")

</div>

Hi,  
In Dynatrace Managed classic Problem notifications → Email, you can only use the placeholders shown under “Available placeholders” in the UI.

```markup
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.

```

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.

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.  
Or&nbsp;in some automation, call Problems API v2 to fetch problem details (includes startTime) and then compose the email.

[Problems API v2](https://docs.dynatrace.com/docs/dynatrace-api/environment-api/problems-v2/problems/get-problem-details)
