Full Image
Integration with Native Monitoring and Application Systems

In addition to assisting the IT room environment monitoring system or other native monitoring systems to enhance insufficient monitoring facilities,
Watchdog can modify or set the original manufacturer environment control system using various functions to provide native environment control or application systems, including various integration methods for their data, messages, or trigger points.
Here are some Watchdog features for integrating with native monitoring and application systems:

Message Types:
➢ Alarm Gateway
Through the alarm gateway function, application systems can uniformly publish abnormal or alarm messages for immediate transmission and control.

➢ Event Alarm
Allows applications to write alarm or abnormal messages into a specified file on the Watchdog host. The system issues or cancels alarm notifications based on the message content.

➢ Mail Forwarding
For information equipment that cannot directly define or modify the alarm system, alarm messages can be forwarded to a specific account on the operations center host via email.

➢ Simple Network Management Protocol - SNMP TRAP
Supports transmitting status values through the SNMP trap channel, enhancing monitoring flexibility and timeliness.

Data Types:
➢ Event Data
Application systems periodically write data into specified files, which are collected and processed by the Watchdog system, including alarm notifications and data analysis. The alarm basis is the value being greater than, less than, or timeout without obtaining data.

Control Types:
➢ Command Gateway
Automatically executes preset commands when issuing or canceling alarms, or manually executes specific commands through the Watchdog tool.
For example: manually triggering emergency shutdown via virtual keys.

Command execution methods include:
(1) Local Commands - issuing commands to the server using an agent program.
(2) IPMI Commands - includes ILO, IMM, iDRAC commands, integrating IPMI into monitoring and issuing commands through the controller.
(3) CLI Commands - issuing commands to the host server using SSH, Telnet, etc.

Moreover, before sending command gateway commands, there are protective mechanisms such as:
Tag Gateway - requires audit tagging to execute the sent command.
SMS Command - requires SMS confirmation to execute the sent command.

Execution Types:
➢ Scheduled Information
The 【Scheduled Information】 function starts programs at specified execution times and writes the obtained information to a file via 【standard output】,
which can be integrated with 【Event Alarm】 or 【Event Data】 to report execution status to Watchdog and check the content of execution.

Main functions include:
1. Collecting records (such as Syslog of specified Event ID)
2. Checking strings that meet alarm conditions in records and issuing alarms
3. Post-processing programs to analyze each collected record (produced as needed)

➢ Screen Snapshot
The main function of screen snapshots is for application systems that cannot transmit data via API or the above methods but still need to monitor their status.
It periodically copies the 【screen】 and sends the image file to the operations center host, monitoring or querying the screen snapshot.
The screen snapshot function can be used for self-capture or agent execution for snapshots of other hosts.

In addition, any type of integration function can trigger the alarm mechanism, not only sending messages based on the notification group but also linking to execute preset commands

Supplementary Information:
Each brand has different names for IPMI, but they essentially use IPMI binding at the underlying level.
IBM -> RSA, RSA2, IMM, IMM2, IPMI, BMC
DELL -> iDRAC
ASUS -> ASMB, ASMB4-iKVM, ASMB5-iKVM
SUN -> ALOM
Fujitsu -> iRMC
HP -> ILO2, ILO3, ILO4 ....



Return to the previous page