I have an B2B application with an SOAP API where customers calls my application and expect answers. When the input is malformed the API returns a HTTP 500 error (which is according to specs I believe) but in the purepath I can see an exception that indicates it is because malformed input (from customers). Since this happens alot and is not our responsibility I would like to be able to filter out that from the problem detection (today I get that raised as problems). I want to have other HTTP 500 to be picked up as problems. Just this "HTTP 500 AND malformed exception" combination needs to be excluded. Is this possible?
In the navigation select "Transactions and Services" then click on the specific service you're interested in. Then when you're on the below page click the "..." and you can edit the service on a page which includes the error detection settings Michael refers to.
Hello Anders, I would rather go the other way around, that not to disturb the OOTB sensors/rules, but create Custom Rules or BT/M to do this instead.
Let me know if you wish to go this way instead, along with details what you wish to achieve.
For counts, create a BT containing with AND logic
1. The HTTP status code equals '500'
2. Create a logging measure with the specific measure Not Containing the exception message.
For alert create a Count threshold measure on logging measure.
For Charting use this BT for count.