I need some help to identify where some of our error-logs are coming from.
It's clear that it belongs to the Circuit Breaker assertion as we are talking about audit-code 11500 "{0} Circuit tripped; open until {1}".
The affected policies have 4-5 Circuit Breaker assertions configured in total and just one of it uses a Custom Event Tracker ID. The Custom ID contains the serviceURI and Client-Cert name to be unique across all policies.
The problem now is, that I just see this single WARNING message without any reference, which Circuit is affected. And even more interesting, the overall status of the error-log entry is "Message processed successfully".
The policy logic is always the following schema:
At least Folder
- Circuit Breaker folder
- Errorhandling if the Circuit Breaker is not active
- Errorhandling if the Circuit Breaker is active
The two errorhandling folders also contain "Add Audit Details"-assertions, but I don't see such messages in the audit-logs. This means for me the Circuit Breaker folder is fully successful and there should be no reason for the Circuit Breaker to be active.
So do you have any idea/explaination of this behavior? Or how can I adjust the policy to get more details?
Thank you!
Ciao Stefan :)