DB Metrics don't show in DX APM investigator
search cancel

DB Metrics don't show in DX APM investigator

book

Article ID: 380059

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

Installed and integrated Precision monitoring (release 3.4) with APM 10.8 on API Gateway version 11,1.

API gateway is installed on appliance with Debian OS

The script "gatewayOSresource-mysql.pl is not able to login in the DB and get the metrics.

I modified the password so is matching the credentials.

In the DX APM Agent (APMIA 23.3) log file I see the following error:

[INFO] [IntroscopeAgent.EPAgent MYSQL] Starting plugin 'MYSQL'.
[ERROR] [IntroscopeAgent.EPAgent MYSQL] [ stderr ] Smartmatch is experimental at /opt/apmia/extensions/apim/bin/gatewayOSResource-mysql.pl line 394.
[ERROR] [IntroscopeAgent.EPAgent MYSQL] [ stderr ] mysql: [Warning] Using a password on the command line interface can be insecure.
[ERROR] [IntroscopeAgent.EPAgent MYSQL] [ stderr ] ERROR 1045 (28000): Access denied for user 'user'@'localhost' (using password: NO)

Resolution

Note that using EPAgent script approach for monitoring MySQL DB is already outdated. It  has been replaced with the newer DX APM releases of APMIA MySQL agent extension as mentioned in CA Precision API Monitoring 3.4.101 release notes  - CA Precision API Monitoring 3.4

 

Note

Gateway 11.x Users
- Users planning to use PAPIM with versions 10.1 or newer of the API Gateway must install the PAPIM 3.4.101 release.
- EPAgent has reached End-of-Service in its product support life cycle. Users using on-prem APM server can now download the API Gateway Infrastructure Agent and are recommended to use SaaS installation for API monitoring. For further details, see SaaS installation.

 

Thus, if you wish to continue with the EPAgent script approach, we would need your assistance to look for a custom workaround or mysql db configuration that could still work with the EPAgent script approach in your environment.  Our dev team would most likely focus on fixing only the latest APMIA MySQL agent extension if a code fix would be required. 

Additional Information

User wanted to specifically use the EPAgent.