Financial services - BR

7/7 2.3 Metrics API The Metrics api uses the Analytics information to extract this info. To get the availability information, the logstash calls the status API each minute to check the current APIs status. The Metrics API could access the backend status API directly using the internal cluster services. The initial suggestion is to keep this way and just increase the pooling interval to 5min. 2.4 Development planning To get this new architecture we need to have the following steps: • Scenario 1 – Creating the healthcheck/alive method for each mock backend api and adjusting the current APIM policy script to call them to get the status. For this we can configure ther backend api and each endpoint test on KPS, so it would be one option. o Developing the healthcheck method for each mock api ~ 1 hour for api. o Adjusting the Policy Script to read the kps to get the test method for each endpoint and call them ~ 2 days. o Adjusting the logstash call to 5 min ~1 day (we need to review this configuration). • Scenario 2 – Using the status backend API (as described above) and the healthcheck/alive method for each mock backend api and adjusting the current APIM policy script to call them to get the status. o Developing the healthcheck method for each mock api ~ 1 hour for api. o Developing the status backend API to call the health check ~ 3 days. o Adjusting the logstash call to 5 min ~1 day (we need to review this configuration). © Axway, 2022

• Cover