Splunk AppDynamics

Create Dashboard Metric for HTTP Error Code With Specific Error Value

Razziq
Explorer

Hello,

We are trying to build a dashboard widget that displays the error count for an HTTP error code 402 that contains a specific value. Is there any way to perform this task, or to create a seperated out 402 value? The only option we have from the widget console is to display all 402s, which does not give us the count for this specific error.

We have an on prem controller on version 4.3.4.7.

Any other suggestions would be great as well!

See screenshot for example.

Thanks!

Labels (1)
0 Karma
1 Solution

Yogesh_Chouk
Builder

Hi Razziq,

As per the screenshot attached, we understand that your requirement is to plot the error count having error code as 402 and message as SECUR-0002 on the dashboard. SECUR-0002 is the error message 

We cannot create a dashboard with specific Error messages. We can plot error count on dashboard for specific errro code as per the attached screenshot.

Please let us know if you have any concerns regarding this.

Thanks,

Yogesh

View solution in original post

0 Karma

Yogesh_Chouk
Builder

Hi Razziq,

As per the screenshot attached, we understand that your requirement is to plot the error count having error code as 402 and message as SECUR-0002 on the dashboard. SECUR-0002 is the error message 

We cannot create a dashboard with specific Error messages. We can plot error count on dashboard for specific errro code as per the attached screenshot.

Please let us know if you have any concerns regarding this.

Thanks,

Yogesh

0 Karma
Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...