Configuring PMI levels in WebSphere Application server to expose Metrics for APM
To monitor a WebSphere Application Server instance using Applications
Manager, you need to enable Performance Monitoring Infrastructure (PMI)
on the server. This will allow the server to expose the required metrics
for monitoring.
PMI is enabled by default, and the default monitoring level is Basic, which is the minimum level required to expose the necessary metrics for monitoring the WebSphere Application Server in Applications Manager.
PMI is enabled by default, and the default monitoring level is Basic, which is the minimum level required to expose the necessary metrics for monitoring the WebSphere Application Server in Applications Manager.
Below the Basic level, level None is available: which if enabled, will expose no data from
the Application Server to be monitored.
Additionally to disable unwanted metrics that are not used by Applications Manager, Custom profiling can be used. To enable Custom profiling, go to the Application Server's console and click on "performance monitoring infrastructure(PMI)" as shown in the below image.
Then click on Custom, as shown in the below image.
The below console will be available and the you can Enable/Disable the required Statistics as per your requirements.
A list of the all Statistics that are utilized in Applications Manager and the corresponding option to be enabled has been provided below:
| MO | Component in WebSphere Application server | Metric in APM | Metric to be enabled in Custom PMI profile |
| Web | Web Applications & Servlet Session Manager | Session Creation/Min | CreateCount(Servlet Session Manager) |
| Affinity Breaks/Min | AffinityBreakCount(Servlet Session Manager) | ||
| Live Sessions | LiveCount(Servlet Session Manager) | ||
| Active Sessions | ActiveCount(Servlet Session Manager) | ||
| Total Requests/Min | RequestCount(Web Applications) | ||
| Error count/Min | ErrorCount(Web Applications) | ||
| Concurrent Requests | ConcurrentRequests(Web Applications) | ||
| EJB | Enterprise Beans | Concurrent Lives | LiveCount |
| Total Method Calls | MethodCallCount | ||
| Average Method Response Time | MethodResponseTime | ||
| Pool size | PooledCount | ||
| Activation time | ActivationTime | ||
| Passivation time | PassivationTime | ||
| Activate Count | ActivateCount | ||
| Servlet | Web Applications | Total Requests | RequestCount |
| Concurrent Requests | ConcurrentRequests | ||
| Error Count | ErrorCount | ||
| Response Time | ServiceTime | ||
| JCA | JCA Connection Pools | Create Count | CreateCount |
| Close Count | CloseCount | ||
| Pool size | PoolSize | ||
| Free Pool size | FreePoolSize | ||
| Use Time(ms) | UseTime | ||
| Wait Time(ms) | WaitTime | ||
| Waiting thread count | WaitingThreadCount | ||
| JDBC | JDBC Connection Pools | Create Count/Min | CreateCount |
| Concurrent Waiters | WaitingThreadCount | ||
| Faults | FaultCount | ||
| Wait Time(Avg) | WaitTime | ||
| Percent Used | PercentUsed | ||
| Percent Maxed | PercentMaxed | ||
| Pool Size | PoolSize | ||
| Free Pool size | FreePoolSize | ||
| JMS | SIB Service & SIB Messaging Engines | Queue Depth | AvailableMessageCount |
| Uncommitted Transactions | UnavailableMessageCount | ||
| Produced Count/Sec | TotalMessagesProducedCount | ||
| Consumed Count/Sec | TotalMessagesConsumedCount | ||
| Number of Producers | LocalProducerCount | ||
| Number of Consumers | LocalConsumerCount | ||
| Message Wait time(sec) | LocalMessageWaitTime | ||
| Oldest Message age(sec) | LocalOldestMessageAge | ||
| Durable Subscriptions | DurableLocalSubscriptionCount | ||
| Non-durable Subscriptions | NonDurableLocalSubscriptionCount | ||
| Incomplete Publications | IncompletePublicationCount | ||
| Oldest Publication Age | LocalOldestPublicationAge | ||
| Number of Publishers | LocalPublisherCount | ||
| Number of Subscriptions | TotalLocalSubscriptionCount | ||
| Number of Publications | TotalMessagesPublishedCount | ||
| Thread | Thread Pools | Thread Creates | CreateCount |
| Thread Destroys | DestroyCount | ||
| Active Threads | ActiveCount | ||
| Percent used | PercentUsed | ||
| Percent maxed | PercentMaxed | ||
| Pool size | PoolSize | ||
| Declared Thread hung count | DeclaredThreadHungCount |
New to ADSelfService Plus?
Related Articles
How data is collected in Applications Manager for IBM WebSphere Application Server?
In Applications Manager, we generally support monitoring for versions 5.x to 9.x, and data collection for each version may differ based on the version of the IBM WebSphere Application Server being monitored. For versions 6.x to 8.x - Data collection ...Uninstrumented Block of Code - APM Insight
In the traces tab --> Slowest Method Calls and Count we show if you find Un-instrumented block of code the reason is as follows: Basically, What is un-instrumented block of code in APM Insight? By default, APM Insight agent monitors known frameworks ...How to rename an existing APM - Java agent application's monitor?
In Applications Manager's APM(Application Performance Monitoring) doesn't support renaming applications/monitors from the web client. However, the application name of an existing application instance can be renamed in the `apminsight.conf` file and ...Self monitor Applications Manager using APM Insight Java Agent
Applications Manager is built with Java, hence we can monitor it using APM Insight Java Agent to measure it's performance continuously, which can be very much useful. Setting up APM Insight Java Agent Follow the below steps to download and set up the ...APM Insight Troubleshooting - FAQs
Monitor Addition - FAQs 1. How to add an APM Insight Monitor? After you deploy the APM Insight agent in your Application Server with suitable Applications Manager credentials in the apminsight.conf file, APM Insight monitors will automatically be ...