After Upgrading the java WebSphere agent version to latest (24.x) the matrix "Backends|Oracle DB" format has changed. Can we get revert back to old format?
Article ID: 378475
Updated On:
Products
Issue/Introduction
After upgrading the APM java WebSphere agent version to 24.x from older version 10.7 >Under Backend we could see Oracle DB are not loading /missing. where as we all the oracle back end call is happening and APM is able to track it. Alerts are configured on this metric so this is important metric to monitor .
Environment
Java agent 24.x
Cause
The newer DX APM versions have improved the db naming in metric name formatter to better address MULTIPLE HOSTS instead of just defaulting to a generic "Oracle DB" name as seen with APM 10.7.
Resolution
How to get the metrics
**************************
After commenting out the following 2 skips in their /opt/WebSphere8.5/wily/releases/24.5/core/config/oraclejdbc.pbd and restarting their monitored app
# Socket data from the Oracle driver reports too many metrics
#SkipPackagePrefixForFlag: oracle.jdbc. SocketTracing
#SkipPackagePrefixForFlag: oracle.net. SocketTracing
expected metrics under "Backends|Oracle DB" with APM 10.7 would now be reported under "Backends|<hostname> (MULTIPLE HOSTS)-xxx (Oracle DB)" with DX APM 24.x versions.
It is because of
The newer DX APM versions have improved the db naming in metric name formatter to better address MULTIPLE HOSTS instead of just defaulting to a generic "Oracle DB" name as seen with APM 10.7.
For alert configuration
*************************
It would be better to just update the old db name "Oracle DB" references in the alert configurations to use the new db names accordingly.
In case want to use old format
*********************************
If the customer would still like to keep using the old db names in their alert configurations, they may consider creating calculated metrics under the previous db name "Oracle DB" for the incoming metrics with "Backends|<hostname> (MULTIPLE HOSTS)-xx (Oracle DB)" in the metric path. Alternatively, another less recommended approach is to look into replacing the {database} macro in the corresponding Backends metric paths in sqlagent.pbd with the hard-coded db name "Oracle DB", but this would have the side effect of all db metrics from various db instances being reported under one generic db name "Oracle DB" instead of their individual db nodes.
Additional Information
So for calculated metrics ,follow the below link.
Feedback
