Grafana / Gateway Service Metrics / Routing Failure

book

Article ID: 221180

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

Needto understand why the counter of "routing failure" is never moving in the Grafana graphs even if I am generating errors of this kind.

Can you explain how the tag "isRoutingFailure" is set to true?

We are using the example gateway deployment from :

https://github.com/CAAPIM/apim-charts/tree/stable/charts/gateway

 

Cause

The Grafana graphs are using data from influxdb which is receiving metrics data from the gateway using the external metrics .

see also :

https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-gateway/congw-10-1/learning-center/overview-of-the-policy-manager/gateway-dashboard/configure-gateway-for-external-service-metrics.html

The API are created from API Portal and are using the default portal policy templates  .or are using custom policy templates where the routing is done in a custom encapsulated assertion .

Environment

Release : 10.0

Component : API GATEWAY

Resolution

By default  a encapsulated assertion is not propagating the routing statistics to the parent policy , therefore the policy will always be flagged as failed due to policy problem .

If you  are doing the routing in a portal published API  template which is a encapsulated assertion  too  or a custom encapsulated assertion .

you have to set the option  "Update routing statistics in parent policy"  in the encapsulated assertion properties . 

This is also not checked for the portal default templates :

- Standard Policy Template - API Key

- Standard Policy Template - No auth

- Standard Policy Template - OAuth.20 .

Right click the policy  "Standard Policy Template Fragment - API Key " select  "encapsulated assertion properties "  on the bottom of the screen select "Update routing statistics in parent policy" and save it 

 

 

Attachments