if I understand it correctly the routing failures shown in the Dashboard are either:
- Requests which are not routed at all (due to FW or network issues) or will be dropped from the backend server.
- Requests which are answered with a HTTP response code >=400.
For some of our services we have lot's of 4xx responses, but which are normal and can't be avoided. Therefor my question is, if it's possible to define the HTTP response codes which should be treated as routing failures and which are fine. And if possible, can this be done on a per-policy basis or just globally?
Thank you for your post. The way that the gateway writes events for the Dashboard it is not controllable by policy. Anytime that the HTTP Routing assertion experiences an error code it will show as a failure. Please log an idea on our community to how you would like the behavior to be.
Stephen HughesBroadcom Support