Splunk AppDynamics

Filter error using HTTP parameter value

Daniel_Extremia
Engager

Hello,

In Configuration -> Instrumentation -> Error Detection 

I do not see a way to exclude errors by HTTP Parameter value... 

We have a customer that has some reported errors that should not be considered errors when there is certain value in an HTTP Parameter value.

Is there a way to achieve this in AppDynamics?


Thanks a lot for support.

Labels (3)
0 Karma
1 Solution

Daniel_Extremia
Engager

As a workaround we managed to filter the related traffic already from instrumentation (by filtering the traffic containing certain HTTP parametre value). 

So as we cannot filter errors we completely filter the traffic containing that HTTP parameter value (so those errors will no longer be considered cause we do not even consider that traffic anymore as business transaction).

View solution in original post

Daniel_Extremia
Engager

As a workaround we managed to filter the related traffic already from instrumentation (by filtering the traffic containing certain HTTP parametre value). 

So as we cannot filter errors we completely filter the traffic containing that HTTP parameter value (so those errors will no longer be considered cause we do not even consider that traffic anymore as business transaction).

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Reuse: Word-play

This puzzle series (first published here) is based on analysing words.Some of the statements in your puzzle ...

Tuning Edge Processor in Hybrid Mode: What Limits Each Data Path

When you run Edge Processor in hybrid mode, alongside a Splunk heavy forwarder on the same host, two questions ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...