IBM DataPower Operations Dashboard v1.0.20.x

A newer version of this product documentation is available.

You are viewing an older version. View latest at IBM DPOD Documentation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Current »

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 Big Data Retention process

  • Dropped syslog messages

  • Dropped WS-M messages

  • Syslog and WS-M agent status

  • Log Target Misconfiguration

  • Log Target Enabled and Down

  • Critical Service

The internal alerts can be published in three ways:

  1. Via Email - from the system parameters page, change the value of "Internal Alerts - Send Email on Alert" to "true", and enter the email destination/s (comma separated) in "Internal Alerts - Email Destination Address for Alerts".

  2. Via Syslog - from the system parameters page, change the value of "Internal Alerts - Send Syslog on Alert" to "true",  the syslog destination is identical to the destination of the normal system alerts, and can be configured from the parameters  "Hostname of the target server for syslog alerts" and "Port of the target server for syslog alerts".

  3. As a notification in the web console, you can change the interval of the alerts from the user preferences page.

Internal Alerts Page

Latest Checks Status Section

Each box represent a check type of the alert and clicking on the box will show 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 (because of a problem with DPOD for example), but a previous check detected a problem.
Grey - The check did not run yet - some checks only start a few minutes to an hour after DPOD starts up - this is normal and does not indicate on any problems.

Filters

  • Start TIme: Show internal alerts by time range.

  • Check Type: Show internal alerts by type

Internal Alerts Grid:

Name

Description

Time

The time where the internal alert was generated

Alert

Description of the internal alert - for example "Syslog agent is down"

Additional info

Any other diagnostic information - for example "Agent Name: SyslogAgent-1"

UUID

An internal UUID , you can search for this UUID in the logs when instructed to do so by support personal


  • No labels