The following P6 EPPM metric data can be displayed in columns of the Enterprise Manager Cloud Control:
P6 Services
These following services correspond to the services you set in the P6 Administrator application:
- All Service Summary
- Apply Actuals
- Leveler
- PX
- Recalc Cost
- Schedule Check
- Scheduler
- Store Period Performance
- Summarizer
For each service, you can view the following metrics:
Metric | Descriptions |
|---|---|
Average Execution Time (secs) | The average time (in seconds) the service took to run. |
Number Currently Running on Target | The number jobs currently running on the node. |
Number of Jobs Currently Running System Wide | The number of jobs currently running on all nodes. The job information displayed represents the status for all job service nodes (based on data in the database). |
Number of Jobs Executed In Last Hour | The number of jobs that finished in the last hour. |
Number of Job Executions | The number of times the job has run. |
Number of Jobs Failed In Last Hour | The number of times the job failed in the last hour. |
Number of Jobs Pending System Wide | The number of jobs waiting to run on all nodes. The job information displayed represents the status for all job service nodes (based on data in the database). |
Additionally, the All Service Summary service includes the following metrics:
- Longest Running Job Type The job that takes the most time to run.
- Max Memory The maximum memory given to the Java process (in kilobytes).
- Shortest Running Job Type The job that takes the least time to run.
- Used Memory The amount of memory that is being used (in kilobytes).
How to Analyze P6 Services
These P6 Services help you to determine if your targets are above capacity or close to it. They also give you the information you need to rework the services to get targets below capacity.
When the ratio of the Number of Jobs Pending System Wide and the Number of Jobs Currently Running System Wide continues to increase, your system might not be able to keep up with demand. You will need to determine which targets are at capacity and which are under-utilized.
- A target is at capacity if the memory it is using equals or is close to the amount of memory available. The Average Execution Time will also increase because the machine does not have enough resources to handle all the running jobs.
- A target is under-utilized if the memory it is using is significantly below the amount of memory available. The Number Currently Running on Target will be low.
When you have identified the targets at capacity and those that are under-utilized, you will need to balance the work among targets. To determine how to balance the system, use the values of your P6 Services, especially those indicating which jobs take the longest and which run most frequently.
If all of your machines are at capacity, you must add new targets.
Connection Pool
Each connection pool type has two sections: information and performance.
- Long-Running SQL Connection Pool Information
- Long-Running SQL Connection Pool Performance
- Regular SQL Connection Pool Information
- Regular SQL Connection Pool Performance
- Transactional SQL Connection Pool Information
- Transactional SQL Connection Pool Performance
The SQL Connection Pool types represent pools of database connections which are used for the following types of database access:
- Long-Running SQL Connection Pool Used for long running transactions, which includes all job services (scheduling, summarizing, apply actuals).
- Regular SQL Connection Pool Used for normal, short-lived transactions, typical of loading data in a web page.
- Transactional SQL Connection Pool Used for transactional operations that usually involve inserting or updating more than 2 tables, and includes all P6 Integration API operations that involve updating data. Used for long delete operations within P6, including deleting projects and EPS objects.
The information section will display your settings as you have set them in the P6 Administrator application. The performance section will tell you how long it takes each service to run.
The performance sections will display the following information:
- Average Lease Time (secs) The average time a user keeps a lease to a connection. If the average lease time over a period of a few days is close to the Maximum Lease Duration setting (for the particular connection pool type), then it may be necessary to increase the Maximum Lease Duration setting to avoid getting database connection lease timeout errors. The user will see these errors as a failure to load a web page or complete an API transaction. These errors will also be seen in the P6 Access logs.
- Average Lease Wait Time (secs) The average time a user must wait for a lease to a connection to become available. If the average lease wait time over a period of a few days is close to the Lease Request Wait Timeout setting (30 seconds is the default for all connection pool types), then it may be necessary to increase the Maximum Connections setting to allow more connections to be available for leasing on a busy system. Another possible cause of a Lease Request Wait Timeout is database connections are being held due to database locks; your database administrator should investigate these locks.
- Average SQL Times (secs) The average time to process SQL queries.
- Connections Allocated The number of connections available to users.
- Connections In Use The number of leased connections that are actively involved in database transactions. If the Connections in Use value is close to the Maximum Connections setting for more than 1 minute, you are exceeding the capacity of your database connection pool, and you are most likely overloading your server with requests. Another possible cause of server overload is database locking; your database administrator should investigate.
- Connections Leased The number of database connections that have been reserved by active user transactions.
- Connections Recycled The number of previously leased connections that have been forcibly returned to the connection pool due to lease timeout while the connection was not in use.
- Connections Revoked The number of previously leased connections that have been forcibly returned to the connection pool due to lease timeout during a database transaction.
- Denied Lease Request The number of database connection lease requests that were denied due to insufficient free database connections. If 'Denied Lease Request' count increases by more than one per day, your database administrator should investigate the database load as it indicates that user transactions are failing due to insufficient number of free database connections for an extended period of time (see Average Lease Wait Time above).
- SQL Queries the number of SQL queries processed.
- Succeeded Lease Requests The number of users who received a lease request.
- Waiting for a Lease The number of users waiting for a lease.
User Session Information
Historical Unique Total Logins: Total number of unique logins
This is the total historic count of unique P6 EPPM users that have logged into the system. This count will never exceed the total number of users in the user dictionary. For each unique user who has logged into the system, you will have only one entry to show they logged in. The purpose is to show how many users in your user dictionary have logged into the system.
Session Counts
These values refer to the number of P6 EPPM sessions currently logged in, based on module access permissions. For example, if a user logs in and has been assigned module access to both Resources and Projects, both the Projects session count and the Resources session count will increment by one. OEM collects counts for the number of:
- API Sessions
- Concurrent Users
- Enterprise Reports Sessions
- Logged in Users
- P6 Analytics Sessions
- P6 Professional Sessions
- Portfolios Sessions
- Projects Sessions
- Resources Sessions
- Team Member Interfaces Sessions
- Team Member Sessions
- Timesheet Sessions
- Total User Sessions
- Web Services Sessions