ePO Server Health

ePO Server Health provides useful details about your ePO server and database. The health timeline shows regularly scheduled status updates.

ePO Server Details

ePO Server Details provides an overview of your ePO server, ePO version, and database.

  • Server Details
  • ePO Details
  • SQL Server Details
  • ePO Database Details
  • ePO Event Database Details

Server Health Timeline

Server Health Timeline provides a visual display of regularly scheduled health checks over time. By default, these checks run hourly and you can modify the schedule using the Server Task page. You can also run a manual health check.

The color coded icons represent each of the checks. The icons describe the type of check and are color coded to indicate the status. Typically, green means the check was successful, yellow that there was a warning, and red that the check failed. You can hover over an icon to view quick details. Click the icon to view more details.

You can view the details of the default and manual health checks in the Audit Log page.

Health Check Details

Health Check Details provides a summary of the selected row in the timeline. It also includes detailed information about each of the specific checks.

Health check details
Option Definition Indicators
ePO Database Connection Check Verifies connectivity between the ePO server and the ePO database server.

Can ePO connect to the database?

  • Successful — Yes
  • Failed — No

ePO Server machine CPU Check Verifies the CPU load of the ePO server.

ePO server CPU load is...

  • Successful — Less than 70%
  • Warning — More than 70%
  • Failed — More than 90%

ePO Server Machine Memory Check Verifies the memory load of the ePO server.

Free memory is...

  • Successful — More than 30%
  • Warning — Less than 30%
  • Failed — Less than 10%

ePO Database CPU Check Verifies the CPU load of the ePO database server.

ePO database server CPU load is...

  • Successful — Less than 70%
  • Warning — More than 70%
  • Failed — More than 90%

ePO Database Index Fragmentation Check Verifies the index fragmentation state of the ePO database.

Index fragmentation is...

  • Successful — Less than 70%
  • Warning — More than 70%

ePO Database Memory Check Verifies the memory load of the ePO database server.

Free memory is...

  • Successful — More than 30%
  • Warning — Less than 30%
  • Failed — Less than 10%

ePO Database Size Check Verifies the free space available on the ePO database server.

Free space is...

  • Successful — More than 30%
  • Warning — Less than 30%
  • Failed — Less than 10%

ePO Application Server JVM Thread Check Verifies the thread status of the ePO Application Server JVM.

Threads timed waiting count and blocked count are...

  • Successful — Less than 100 and 0
  • Warning — More than 100 and 0
  • Failed — More than 100 and more than 0

ePO Application Server JVM CPU Check Verifies the CPU load of the ePO Application Server JVM.

ePO Application Server JVM CPU load is...

  • Successful — Less than 70%
  • Warning — More than 70%
  • Failed — More than 90%

ePO Application Server JVM Memory Check Verifies the memory load of the ePO Application Server JVM.

Free memory is...

  • Successful — More than 30%
  • Warning — Less than 30%
  • Failed — Less than 10%

Data Channel Waiting Queue Check Verifies the waiting queue load for data channel messages.

Waiting count is...

  • Successful — Less than 5
  • Warning — More than 5

Event Parser Failing Check Verifies the ePO Event Parser failing count.

Failing count is...

  • Successful — Equal to 0
  • Failed — More than 0

Event Parser Waiting Check Verifies the waiting queue load of the ePO Event Parser.

Waiting count is...

  • Successful — Less than 50
  • Warning — More than 50

Failing Server Tasks Check Verifies whether server tasks have been failing in the last 7 days.

Tasks are failing?

  • Successful — No
  • Failed — Yes

Waiting Server Tasks Check Verifies whether server tasks have been in a waiting state from more than an hour at the time of the check.

Tasks are in a waiting state for more than an hour?

  • Successful — No
  • Warning — Yes