# Reasons for failed requests - Plot over time?

**URL:** <https://community.dynatrace.com/t/reasons-for-failed-requests-plot-over-time/35459>\
**Category:** Open Q&A\
**Tags:** request-attributes, multidimensional-analysis\
**Created:** [June 13, 2022, 1:18am UTC](https://community.dynatrace.com/t/reasons-for-failed-requests-plot-over-time/35459 "2022-06-13T01:18:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![benjamin\_mullan](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/benjamin_mullan/32/38132_2.png) [@benjamin\_mullan](https://community.dynatrace.com/u/benjamin_mullan)\
**Post date:** [June 13, 2022, 1:18am UTC](https://community.dynatrace.com/t/reasons-for-failed-requests-plot-over-time/35459/1 "2022-06-13T01:18:45Z")

</div>

Dynatrace allows me to plot an exception over time as below.

 ![benjamin_mullan_1-1655082968790.png](https://global.discourse-cdn.com/dynatrace/original/3X/b/4/b4b2fbde5e8b091eb699b7de5a422c58af88103f.png)

Is there a way to plot or query the Message within the exception over time like the below?

 ![benjamin_mullan_0-1655082928873.png](https://global.discourse-cdn.com/dynatrace/original/3X/0/b/0b0783a7f1dd7575215e7a69137f6b9c94c48125.png)

---

<div class="post-metadata">

**Author:** ![uros\_djukic1](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/uros_djukic1/32/37084_2.png) [@uros\_djukic1](https://community.dynatrace.com/u/uros_djukic1)\
**Post date:** [June 13, 2022, 8:14am UTC](https://community.dynatrace.com/t/reasons-for-failed-requests-plot-over-time/35459/2 "2022-06-13T08:14:36Z")

</div>

Hello Benjamin,

To answer you quickly, yes it is possible via Request Attribute.&nbsp;  
Thus, to have to do this properly, you have to select your Exception class name, please see below the screenshot :

 ![uros_djukic1_0-1655108010739.png](https://global.discourse-cdn.com/dynatrace/original/3X/9/9/991c49258fdefe3a451d4028aeaed374760d1d55.png)

Afterward, you will be able to plot onto your MDA chart as new detected placeholder, and eventually convert to custom metrics (calculated service metrics).&nbsp;  
Thanks

---

<div class="post-metadata">

**Author:** ![benjamin\_mullan](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/benjamin_mullan/32/38132_2.png) [@benjamin\_mullan](https://community.dynatrace.com/u/benjamin_mullan)\
**Post date:** [June 13, 2022, 9:36pm UTC](https://community.dynatrace.com/t/reasons-for-failed-requests-plot-over-time/35459/3 "2022-06-13T21:36:51Z")

</div>

Alas! I am using Node.js and cannot find the corresponding&nbsp;Request attribute source as you have shown for Java.

I’m assuming for Node.js the SDK approach is going to be suggested.

 ![benjamin_mullan_0-1655156167475.png](https://global.discourse-cdn.com/dynatrace/original/3X/e/6/e6aa6a796cd2aa1ae5a95b7b81580131fbef1279.png)

Thanks for the Information. I consider it answered for “supported technologies”

---

<div class="post-metadata">

**Author:** ![uros\_djukic1](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/uros_djukic1/32/37084_2.png) [@uros\_djukic1](https://community.dynatrace.com/u/uros_djukic1)\
**Post date:** [June 14, 2022, 7:51am UTC](https://community.dynatrace.com/t/reasons-for-failed-requests-plot-over-time/35459/4 "2022-06-14T07:51:20Z")

</div>

Yes indeed, need to do some customisation here.&nbsp;  
[Capture any request attributes using OneAgent SDK | Dynatrace news](https://www.dynatrace.com/news/blog/capture-any-request-attributes-using-oneagent-sdk/#:~:text=Configure%20request%20attributes%20in%20Dynatrace%20To%20configure%20a,%28Text%2C%20Integer%2C%20or%20Double%29%20and%20specify%20additional%20settings.)  
Github link :&nbsp;[GitHub - Dynatrace/OneAgent-SDK-for-NodeJs: Enables custom tracing of Node.js applications in Dynatrace · GitHub](https://github.com/Dynatrace/OneAgent-SDK-for-NodeJs#set-custom-request-attributes)

Thanks

---

<div class="post-metadata">

**Author:** ![benjamin\_mullan](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/benjamin_mullan/32/38132_2.png) [@benjamin\_mullan](https://community.dynatrace.com/u/benjamin_mullan)\
**Post date:** [September 15, 2022, 10:40pm UTC](https://community.dynatrace.com/t/reasons-for-failed-requests-plot-over-time/35459/5 "2022-09-15T22:40:05Z")

</div>

I have found another approach for nodeJS.

Create an exception based custom metric and in the advanced settings it allows you to split by  
Exception:Message

 ![benjamin_mullan_0-1663281597097.png](https://global.discourse-cdn.com/dynatrace/original/2X/4/4cee8cd98e8a1b284283cd8a1333fd099acbd957.png)

---

<div class="post-metadata">

**Author:** ![uros\_djukic1](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/uros_djukic1/32/37084_2.png) [@uros\_djukic1](https://community.dynatrace.com/u/uros_djukic1)\
**Post date:** [September 23, 2022, 9:46am UTC](https://community.dynatrace.com/t/reasons-for-failed-requests-plot-over-time/35459/6 "2022-09-23T09:46:36Z")

</div>

Hi&nbsp;[@benjamin\_mullan](https://community.dynatrace.com/user/36325)&nbsp;,  
Thanks for sharing, yes indeed you can use by custom metric (Calculated service metric), only if your dimension {Exception:Message} has enough parameters to get it. Otherwise, you have to configure via Request Attribute to deep dive on it and hope to pull more content into parameter.
