Configuring PMI levels in WebSphere Application server to expose Metrics for APM

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.

 Below the Basic level, level None is availablewhich 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:

MOComponent in WebSphere Application serverMetric in APMMetric to be enabled in Custom PMI profile
WebWeb Applications & Servlet Session ManagerSession Creation/MinCreateCount(Servlet Session Manager)
Affinity Breaks/MinAffinityBreakCount(Servlet Session Manager)
Live SessionsLiveCount(Servlet Session Manager)
Active SessionsActiveCount(Servlet Session Manager)
Total Requests/MinRequestCount(Web Applications)
Error count/MinErrorCount(Web Applications)
Concurrent RequestsConcurrentRequests(Web Applications)
EJBEnterprise BeansConcurrent LivesLiveCount
Total Method CallsMethodCallCount
Average Method Response TimeMethodResponseTime
Pool sizePooledCount
Activation timeActivationTime
Passivation timePassivationTime
Activate CountActivateCount
ServletWeb ApplicationsTotal RequestsRequestCount
Concurrent RequestsConcurrentRequests
Error CountErrorCount
Response TimeServiceTime
JCAJCA Connection PoolsCreate CountCreateCount
Close CountCloseCount
Pool sizePoolSize
Free Pool sizeFreePoolSize
Use Time(ms)UseTime
Wait Time(ms)WaitTime
Waiting thread countWaitingThreadCount
JDBCJDBC Connection PoolsCreate Count/MinCreateCount
Concurrent WaitersWaitingThreadCount
FaultsFaultCount
Wait Time(Avg)WaitTime
Percent UsedPercentUsed
Percent MaxedPercentMaxed
Pool SizePoolSize
Free Pool sizeFreePoolSize
JMSSIB Service & SIB Messaging EnginesQueue DepthAvailableMessageCount
Uncommitted TransactionsUnavailableMessageCount
Produced Count/SecTotalMessagesProducedCount
Consumed Count/SecTotalMessagesConsumedCount
Number of ProducersLocalProducerCount
Number of ConsumersLocalConsumerCount
Message Wait time(sec)LocalMessageWaitTime
Oldest Message age(sec)LocalOldestMessageAge
Durable SubscriptionsDurableLocalSubscriptionCount
Non-durable SubscriptionsNonDurableLocalSubscriptionCount
Incomplete PublicationsIncompletePublicationCount
Oldest Publication AgeLocalOldestPublicationAge
Number of PublishersLocalPublisherCount
Number of SubscriptionsTotalLocalSubscriptionCount
Number of PublicationsTotalMessagesPublishedCount
Thread Thread PoolsThread CreatesCreateCount
Thread DestroysDestroyCount
Active ThreadsActiveCount
Percent usedPercentUsed
Percent maxedPercentMaxed
Pool sizePoolSize
Declared Thread hung countDeclaredThreadHungCount

                    New to ADSelfService Plus?