DPOD automatically runs several self diagnostic tests (checks) on the following internal components:

• Config Database availability

• Config Database size

• Store Nodes status

• File system free space

• Internal Store Retention process

• Dropped Syslog messages

• Dropped WS-M messages

• Syslog and WS-M agent status

• Log Target Misconfiguration

• Log Target Enabled and Down

• Critical Services

Internal Alerts Page

Latest Checks Status Section

Each box represent a check type of the alert and clicking on the box will allow you to see only the relevant internal alerts in the grid below.

The boxes are color coded as follows:

• Green - No problems detected.

• Red - One or more issues were detected, or the previous schedule check did not run (e.g.: because of a problem with DPOD), but a previous check detected a problem.

• Grey - The check did not run yet - some checks only start a few minutes and up to an hour after DPOD starts up - this is normal and does not indicate a problem.

Filters

• Start Time: Show internal alerts by a time range in the grid below.

• Check Type: Show internal alerts by type in the grid below.

Internal Alerts Grid

Internal Alerts in the Web Console

Internal alerts will be displayed as notifications to the Web Console administrator.

See internal alerts field in User Preferences page for configuring the notifications.

Internal Alerts Publishing

The internal alerts can be published via the following facilities:

• Email - an email will be sent for every generated alert.
  Make sure that "Internal Alerts - Send Email on Alert” is set to true and “Internal Alerts - Email Destination Address for Alerts“ is configured in the System Parameters page.
  The SMTP parameters are configured in the System Parameters page.

• HTTP Request - an HTTP request will be sent for every generated alert.
  Make sure that "Internal Alerts - Send HTTP on Alert" is set to true in the System Parameters page.
  The HTTP request parameters are configured in the System Parameters page.
  For further details about the format of the HTTP request see Alerts JSON Format.

• Syslog message (JSON Format) - a Syslog message will be sent for every generated alert.
  Make sure that "Internal Alerts - Send Syslog on Alert (JSON Format)" is set to true in the System Parameters page.
  The Syslog parameters are configured in the System Parameters page.
  For further details about the format of the Syslog message see Alerts JSON Format.

• Syslog message (Legacy Format) - a Syslog message will be sent for every generated alert.
  Make sure that "Internal Alerts - Send Syslog on Alert (Legacy Format)" is set to true in the System Parameters page.
  The Syslog parameters are configured in the System Parameters page.
  For further details about the format of the Syslog message see below.

• Web Service - a SOAP message will be sent for every generated alert.
  Make sure that "Internal Alerts - Send Email on Alert via Web Service" is set to true in the System Parameters page.
  The Web Service parameters are configured in the System Parameters page.

Internal Alerts Syslog Message Legacy Format

An example of an internal alert sent via Syslog legacy format:

Possible AlertContent values:

• Cannot connect to DB

• Query failed from DB

• Not enough space in mount point

• A critical directory was not found in filesystem

• Store cluster status is red

• Could not connect to the Store

• Syslog agent is down

• WS-M agent is down

• Messaging agent is down

• Agent dropped Syslog messages

• Agent dropped WS-M messages

• The Store retention process is not working

• Database table exceeding threshold size

• Publishing a message to mail/syslog failed

• A post upgrade configuration failed - please re-setup log targets on all monitored devices from the Manage menu

• Found a misconfigured log target, please setup Syslog again for the device

• Found log target(s) in a down state, setting up Syslog for the device might provide more information

• A critical service is not working

• Reindex execution failed

• Cloud agent interact failure