Performance Monitoring

this section describes how to monitor the performance of ivanti service manager monitoring the performance of servers docid 4rfdu7pyntk5v90zxltarmonitoring the processing services docid 4rfdu7pyntk5v90zxltar monitoring the performance of servers if you experience performance issues, such as long delays or timeouts, start diagnostics by monitoring the resources used on your system the following performance monitors provide metrics that you can use to determine if system resources are over utilized on the ivanti service manager application server, monitor the cpu, memory, io, and network on the ivanti service manager database server, monitor the cpu, memory, io, and network plus database statistics also monitor resource utilization for example, if the average cpu utilization is above 60%, consider adding more cpu on the ivanti service manager application server the following are the performance counters on the ivanti service manager application servers the system samples these counters every five minutes and sends the results memory available mbytes paging file percent usage physical disk average disk reads per second average disk writes per second disk reads per second disk writes per second processor percent processor time (cpu) system processor queue length network utilization total, sent, and received per second the following are the performance counters on the ivanti service manager database server memory available mbytes paging file percent usage physical disk average disk reads per second average disk writes per second disk reads per second disk writes per second processor percent of processor time microsoft sql server logins per second logouts per second lock waits per second total latch wait time (ms) total latch waits per second buffer manager page life expectancy general statistics – user connections memory manager – memory grants pending microsoft sql statistics – batch requests per second microsoft sql statistics – compilations per second microsoft sql statistics – recompilations per second system processor queue length average wait time number of deadlocks per second lock timeouts per second monitoring the processing services about monitoring the processing services docid 4rfdu7pyntk5v90zxltarworkflow service docid 4rfdu7pyntk5v90zxltaremail service docid 4rfdu7pyntk5v90zxltarescalation service docid 4rfdu7pyntk5v90zxltarmessage queue docid 4rfdu7pyntk5v90zxltar about monitoring the processing services you also should monitor the processing services the ivanti service manager platform includes built in performance counters for the ivanti service manager message queue, the email service, the escalation service, and the workflow service to manage the processing services more effectively, the system implements counters these counters are implemented per landscape, rather than per service across multiple landscapes each of the counters indicates the output across all servers for example, the system monitors the counter called “number of tenants” for all servers in the landscape where the service is running this provides a holistic view of all of the servers and how the service is distributed and consumed for example, with the workflow service, it shows how the tenants are partitioned versus the non partitioned servers that act as a catch all entity workflow service the workflow service has these monitors counter description events handled per poll represents the number of events read and handled, per tenant, per poll if a tenant does not have any events queued, this is zero events handled per second the number of events read and handled, per tenant, per second events handled versus read per poll percentage the number of events handled, versus read, per tenant, per poll percentage events read per poll the number of events read, per tenant, per poll events read per second the number of events read, per tenant, per second number of busy processor threads based on the configured number of processors of the workflow service on a particular server, in the workflowservice exe config file, the counter shows the number of busy processors available per server the “number of free processor threads” plus the “number of busy processor threads” should equal the total number of processors in the configuration file number of free processor threads based on the configured number of processors of the workflow service on a particular server, in the workflowservice exe config file, the counter shows the number of free processors available per server the “number of free processor threads” plus the “number of busy processor threads” should equal the total number of processors in the configuration file number of outstanding web service calls the number of outstanding web service calls number of tenants the number of tenants assigned to the workflow service, per server based on partitioning, the number should indicate the total number of active tenants on the landscape email service the email service has these monitors counter description number of busy mailbox poll threads number of busy (consumed) mailbox polling threads, per server the “number of free mailbox poll threads” plus the “number of busy mailbox poll threads” should equal the total number of mailbox poll threads as configured in the configuration file number of busy message processing threads number of busy (consumed) message processing threads available, per server the “number of free message processing threads” plus the “number of busy message processing threads” should equal the total number of message processing threads as configured in the configuration file number of emails read the number of emails read from customer mailboxes, per tenant number of free mailbox poll threads number of free mailbox polling threads available, per server the “number of free mailbox poll threads” plus the “number of busy mailbox poll threads” should equal the total number of mailbox poll threads as configured in the configuration file number of free message processing threads number of free message processing threads available, per server the “number of free message processing threads” plus the “number of busy message processing threads” should equal the total number of message processing threads as configured in the configuration file number of messages read the number of email messages read from the database, per tenant number of outstanding web service calls the number of outstanding web service calls number of polled mailboxes the number of mailboxes polled number of tenants the number of tenants assigned to the email service, per server based on partitioning, the number should indicate the total number of active tenants on the landscape escalation service the escalation service has these monitors counter description events handled per poll represents the number of events read and handled, per tenant, per poll if a tenant does not have any events queued, this is zero events handled per second the number of events read and handled, per tenant, per second events handled versus read per poll percentage the number of events handled, versus read, per tenant, per poll percentage events read per poll the number of events read, per tenant, per poll events read per second the number of events read, per tenant, per second number of busy processor threads based on the configured number of processors of the escalation service on a particular server, in the escalationservice exe config file, the counter shows the number of busy processors available per server the “number of free processor threads” plus the “number of busy processor threads” should equal the total number of processors in the configuration file number of free processor threads based on the configured number of processors of the escalation service on a particular server, in the escalationservice exe config file, the counter shows the number of free processors available per server the “number of free processor threads” plus the “number of busy processor threads” should equal the total number of processors in the configuration file number of outstanding web service calls the number of outstanding web service calls number of tenants the number of tenants assigned to the escalation service, per server message queue the ivanti service manager message queue has these performance monitors counter description average message processing time the average time for a message to be processed by a handler this does not account for the time that the message spends in the message queue waiting to be dispatched average message size the average size of the messages received messages created per second the number of messages received, per second messages processed per second the number of messages processed, per second by all handlers number of concurrent handlers the number of handlers that are busy working on items at any given time number of concurrent messages the number of messages that are being processed (dispatched to its handler) at any given time number of outstanding web service calls the number of outstanding web service calls number of tenants the number of tenants assigned to the message queue server