Versions Compared

Version Old Version 17 New Version Current
Changes made by

Avi Falah

Avi Falah

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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:

...

Internal Alerts

...

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".

...

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

...

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

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

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

Publishing Internal Alerts

Publishing Internal Alerts to Web Console

See internal alerts field in User Preferences page.

Publishing Internal Alerts via E-Mail

  1. Navigate to System Parameters page.

  2. Update the following parameters:

    1. Set Internal Alerts - Send Email on Alert to true.

    2. Set Internal Alerts - Email Destination Address for Alerts to the required e-mail address.

    3. Fill theEmail SMTP category parameters with your organization SMTP e-mail server details.

Publishing Internal Alerts via Syslog Messages

Internal alerts can be published to other systems via Syslog messages by follwing this steps:

  1. Navigate to System Parameters page.

  2. Update the following parameters:

    1. Set Internal Alerts - Send Syslog on Alert to true.

    2. Set Alerts Syslog Server Hostname to the required host name or IP address.

    3. Set Alerts Syslog Server Port to the required port number.

    4. Set Syslog Severity Field Value to the required severity level (info, warn, error, etc).

Internal Alerts Syslog Message Format

Code Block
<16>Mar 14 13:26:22 ${hostname} [0x00a0002a][DPOD-internal-alert][info] AlertContent:(A critical directory was not found in filesystem) AlertUUID:(d44b291e-efda-4236-bd2c-8de0ab1d4e3d) AdditionalInfo:(Mount Point: /logs)

${hostname}

DPOD server hostname

[0x00a0002a]

The message ID for all alerts will always be 0x00a0002a

[info]

The message level may be set via the system parameter.

List of 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