Precision API Monitoring - APM integration limitations and enhancements
Article ID: 185775
Updated On:
Products
CA Application Performance Management (APM / Wily / Introscope)
DX Application Performance Management
Issue/Introduction
This article describes issues and limitations in current PAPIM to APM integration:
1.DE403545: Experience cards are having duplicate cards
2.DE403539: Monitoring should be considered as infrastructure Agent
3.DE403536: Metrics are available at two different places and from ATC we are going to frontend but not under services
4.DE403534: All API's are coming on the leftmost(map view) as a frontend metrics and again after gateway node
5.DE441376: APM backends metrics
1.DE403545: Experience cards are having duplicate cards
2.DE403539: Monitoring should be considered as infrastructure Agent
3.DE403536: Metrics are available at two different places and from ATC we are going to frontend but not under services
4.DE403534: All API's are coming on the leftmost(map view) as a frontend metrics and again after gateway node
5.DE441376: APM backends metrics
Environment
APM 10.7.x
PRECISION API MONITORING 3.4
PRECISION API MONITORING 3.4
Cause
Below enhancements requests have been created for these current issues and limitations:
- US580520 / F95360 - APIM Enhancements for Aggregation metrics at Service level & correlation of TT for APIM
- DE441376 - PAPIM - APM backends metrics
- US580520 / F95360 - APIM Enhancements for Aggregation metrics at Service level & correlation of TT for APIM
- DE441376 - PAPIM - APM backends metrics
Resolution
1.DE403545: Experience cards are having duplicate cards
When user create experience cards with gateway hosts user will be getting two cards - one is default and the other as APIs
Once the user drill down to default experience user will have the gateway and apis cards again
2.DE403539: Monitoring should be considered as infrastructure Agent
APIM monitoring should be considered as a infrastructure Agent,at present APIM monitoring is coming as a Application monitoring.
We would need the application to gateway correlation .
Need to have relevant ICON for the PAPIM gateway
3.DE403536: Metrics are available at two different places and from ATC we are going to frontend but not under services
PAPIM_APM-Metrics are available at two different places: one under frontend and the other under services
Due to this when user select on the node from the metric browser we are only able to view metrics of the node which are under frontend and we are missing the metrics under services
Need to have all the metrics under services
4.DE403534: All API's are coming on the leftmost(map view) as a frontend metrics and again after gateway node
In APIM to APM integration all the API's are coming on the leftmost in Map view as API's are hosted on the APIM Gateway and these metrics on the PAPIM should be coming as a infrastructure metrics
These should be identified on the graph from gateway.
5.DE441376: APM backends metrics
Use-case: for Tomcat installations, the investigator view shows per-backend statistics (including HTTP/LDAP/JDBC Backends). I couldn’t find this view for the Gateway
As of now, PAPIM collects and sends metrics (success, policy faults, routings failures, front end response time, back-end response time, total) for the selected services. All of them are at the service level.
None of them can be attributed to any of the backends used in the services.
When user create experience cards with gateway hosts user will be getting two cards - one is default and the other as APIs
Once the user drill down to default experience user will have the gateway and apis cards again
2.DE403539: Monitoring should be considered as infrastructure Agent
APIM monitoring should be considered as a infrastructure Agent,at present APIM monitoring is coming as a Application monitoring.
We would need the application to gateway correlation .
Need to have relevant ICON for the PAPIM gateway
3.DE403536: Metrics are available at two different places and from ATC we are going to frontend but not under services
PAPIM_APM-Metrics are available at two different places: one under frontend and the other under services
Due to this when user select on the node from the metric browser we are only able to view metrics of the node which are under frontend and we are missing the metrics under services
Need to have all the metrics under services
4.DE403534: All API's are coming on the leftmost(map view) as a frontend metrics and again after gateway node
In APIM to APM integration all the API's are coming on the leftmost in Map view as API's are hosted on the APIM Gateway and these metrics on the PAPIM should be coming as a infrastructure metrics
These should be identified on the graph from gateway.
5.DE441376: APM backends metrics
Use-case: for Tomcat installations, the investigator view shows per-backend statistics (including HTTP/LDAP/JDBC Backends). I couldn’t find this view for the Gateway
As of now, PAPIM collects and sends metrics (success, policy faults, routings failures, front end response time, back-end response time, total) for the selected services. All of them are at the service level.
None of them can be attributed to any of the backends used in the services.
Additional Information
Attachments
Feedback
Yes
No
Powered by
