topic Re: Including starttime in the Dynatrace problem notification in Alerting

Including starttime in the Dynatrace problem notification

moses_chacko — Mon, 13 Dec 2021 15:19:36 GMT

Is there a placeholder that will I can add to show the starttime and end time of problem.

Thanks

Moses

Re: Including starttime in the Dynatrace problem notification

skrystosik — Sat, 27 Apr 2019 11:33:06 GMT

There is new placeholder that is containing html. Check this one, but there is no extra placeholder only for timings.

Sebastian

Re: Including starttime in the Dynatrace problem notification

sumitthakur1989 — Sun, 28 Apr 2019 22:56:19 GMT

Link please

Re: Including starttime in the Dynatrace problem notification

skrystosik — Mon, 29 Apr 2019 04:50:35 GMT

Go to go example service now integration on your tenant, there is list of placeholders

Sebasti

Re: Including starttime in the Dynatrace problem notification

moses_chacko — Tue, 30 Apr 2019 12:05:51 GMT

@sebastian k. did you mean {ProblemDetailsHTML}. If so it does not include the start or end times.

Re: Including starttime in the Dynatrace problem notification

skrystosik — Tue, 30 Apr 2019 12:10:14 GMT

If not I have no idea, I've didn't test it. It was last chance to find it somewhere. Post an RFE for placeholders 🙂 For now you can only get problem ID from webhook and then access start time via API.

Sebastian

Re: Including starttime in the Dynatrace problem notification

MaciejNeumann — Wed, 07 Jun 2023 12:07:32 GMT

Here is the most recent list of available placeholders for problem notifications for email integration:

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 are no placeholders for the start and end times for the moment. You can create a Product Idea in the forum, and we'll make sure to mark one of our PMs to take a look at it 🙂