Cisco Cisco Process Orchestrator 3.0 Betriebsanweisung
5-19
Cisco Process Orchestrator User Guide
OL-30196-01
Chapter 5 Managing High Availability and Resiliency
Windows Performance Counters
Windows Performance Counters
A Cisco Process Orchestrator server publishes performance counters that can be used to monitor its
health and diagnose performance issues. These counters are grouped into several performance objects,
which are discussed in the following sections.
health and diagnose performance issues. These counters are grouped into several performance objects,
which are discussed in the following sections.
The following standard Windows performance counters are also of interest:
•
Memory—Pages/sec
•
Processor—% Processor Time
•
Process—Private Bytes
•
Process—Handle Counts
•
Physical Disk
Cisco Process Orchestrator Object
Table 5-3
Windows Performance Counters - Cisco Process Orchestrator
Counter
Description
Running Process
Instances
Instances
The number of running process instances
Running Activity
Instances
Instances
The number of running activity instances
In-Memory Activity
Instances
Instances
The number of in-memory activity instances.
An in-memory activity instance might be running now or have run
within a process that is running now. For example, if you have a single
10-step sequential process, there will always be only one active activity
instance. But as the workflow continues to run, the number of
“in-memory” activities will grow as the execution progresses. When the
process stops running, the number drops to zero.
within a process that is running now. For example, if you have a single
10-step sequential process, there will always be only one active activity
instance. But as the workflow continues to run, the number of
“in-memory” activities will grow as the execution progresses. When the
process stops running, the number drops to zero.
In-Memory Process
Instances
Instances
The number of in-memory process instances.
In-memory activity instance might be running now, or have run within
a process which is running now. For example, if you have a single
10-step sequential process, there will always be only one active activity
instance. But as workflow continues to run the number of “in-memory”
activities will grow as the execution progresses. When the process stops
running, the number drops to zero.
a process which is running now. For example, if you have a single
10-step sequential process, there will always be only one active activity
instance. But as workflow continues to run the number of “in-memory”
activities will grow as the execution progresses. When the process stops
running, the number drops to zero.
Schedules Monitored
The number of schedules being monitored in Process Orchestrator.
Schedules Met
The number of monitored schedules met in Process Orchestrator.
If there is only one process definition that has an “Every day, every 5
minutes” schedule trigger, then “Schedules Monitored” will be 1 for as
long as the server runs. “Schedules Met” will grow by one every five
minutes as the schedule fires process instances.
minutes” schedule trigger, then “Schedules Monitored” will be 1 for as
long as the server runs. “Schedules Met” will grow by one every five
minutes as the schedule fires process instances.
Events Monitored
The number of events being monitored in Process Orchestrator.