We noticed that the amount of errormessages shown on the SLM Summary Status page does not correspond to the amount of actual errors a service encountered. When reproducing this we noticed that when the backend responds with a soap-fault, SLM classifies this automatically as an error, while in reality this is in most cases an expected response that is handled in the response rule...
Is it possible to modify the criteria that SLM uses to mark a message as an error? Or is there another way to avoid this behaviour?
This topic has been locked.
2 replies Latest Post - 2012-12-14T11:07:22Z by SystemAdmin
Pinned topic SLM message errors
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-12-14T11:07:22Z at 2012-12-14T11:07:22Z by SystemAdmin