Cloud Monitoring Solution (NIMBUS Watch)

Efficient and versatile monitoring technology

• Ping monitoring: Uses Ping to check if the host is still online providing services.
• Port monitoring: Checks if a specific port can be accessed normally (TCP/UDP).
• Web URL monitoring: Checks if a Web URL is functioning correctly (can be determined by Status Code, Response Header, Response Content).
• Windows Service monitoring: Checks if a Windows Service is running properly.
• IIS Application Pool monitoring: Checks if an Application Pool is operating correctly.
• Windows Event Viewer monitoring: Users can monitor specific events in the Event Log on the target server. Alerts are issued when errors occur.
• SQL Server Connection monitoring: Users can monitor specified databases to see if they are running properly, including login and query operations.
• Windows Disk Space monitoring: Users can monitor the remaining space of specific disks on the target server, issuing alerts if below threshold.
• Windows Performance monitoring: Users can monitor six performance indicators on the target server (CPU, Memory, Disk I/O, Network I/O, etc.). Alerts are issued if thresholds are exceeded.
• Custom Push Notification (API) monitoring: Users can generate a token for authentication to send messages to NIMBUS Watch, which pushes the message.
• SQL Server Transaction Log Size monitoring: Users can monitor the transaction log size of databases on a SQL Server and set alert thresholds.
• SQL Server Job Schedule monitoring: Users can monitor SQL Agent jobs on a target SQL Server to check if they are disabled or have failed recently.
• SQL Server Data Lock monitoring: Users can monitor data lock situations in SQL Server databases and set alert thresholds based on lock time.
• Execute SQL Command monitoring: Users can monitor a target SQL Server by executing commands to check if returned results match predefined rules.
• Windows Task Schedule monitoring: Users can monitor the Windows Task Schedule on a target server to check for disabled tasks or recent execution anomalies.
• Advanced Windows Performance monitoring: Users can monitor specific performance indicators on the target server and set custom objects, instances, and counters. Alerts are issued if conditions are not met.
• Advanced Windows Event Viewer monitoring: Users can monitor specific events in the Event Log on the target server, including Windows, application, and service logs. Alerts are issued when errors occur.
• ODBC DSN Connection monitoring: Users can monitor ODBC data sources configured on the target server, issuing alerts when connections fail or response times exceed thresholds.
• Windows File Existence Time monitoring: Users can monitor folders on the target server for file creation, modification, or access dates, issuing alerts if conditions exceed thresholds.
• Web Post monitoring: Sends a request to a URL via HTTP Post and receives the response, checking if it meets user-defined success criteria.
• Ceph OSD Daemon monitoring: Users can monitor the status of Ceph OSD Daemons on the target server (Linux), issuing alerts when the status is abnormal.
• SNMP Disk Space monitoring: Users can monitor disk space on a target server via Simple Network Management Protocol (SNMP), issuing alerts if space is below thresholds.
• SNMP Performance monitoring: Users can monitor CPU and Memory performance indicators on a target server via SNMP, issuing alerts if thresholds are exceeded.
• SNMP Network Traffic monitoring: Users can monitor specific network interface traffic on a target server via SNMP, issuing alerts if input or output traffic exceeds thresholds.
• IPMI Sensor monitoring: Users can monitor hard disk and power supply sensors on the target server via Intelligent Platform Management Interface (IPMI), issuing alerts when sensor readings differ from set values.
• IPMI OS Boot Monitoring: Users can monitor OS Boot events on the target server through the Intelligent Platform Management Interface (IPMI). Alerts will be sent if there are OS Boot events within the monitoring interval.
• Zabbix Alert Monitoring: Integrates with the monitoring software Zabbix. It can retrieve alert information triggered by Zabbix based on the user's entered Zabbix host and permissions, and send alert messages to the user's mobile device via NIMBUS Watch.
• MySQL Connection Monitoring: Users can monitor a specified database to check if it is operating normally. Besides attempting to log in to the database, it also performs query operations to ensure the database is genuinely running correctly.
• MySQL Data Lock Monitoring: Users can monitor if there is data locking (Lock) on the MySQL server database and set threshold values. An alert notification will be sent if the locking time exceeds the threshold.
• MySQL Job Scheduling Monitoring: Users can monitor whether the Event on the target MySQL server is disabled. If it is disabled, an alert notification will be sent.
• Port Monitoring: Check if a specific port is accessible (TCP/UDP).
• Web URL Monitoring: Check if a web URL is functioning properly (based on Status Code, Response Header, Response Content).
• Windows Service Monitoring: Check if a Windows Service is running properly.
• IIS Application Pool Monitoring: Check if an Application Pool is functioning properly.
• Windows Event Viewer Monitoring: Monitor specific events in the Event Log on the target server, including only Windows logs. Alerts are issued when error events are detected.
• SQL Server Connection Monitoring: Monitor specified databases to ensure they are operating correctly. This includes login attempts and query operations to confirm proper functioning.
• Windows Disk Space Monitoring: Monitor the remaining space on specific disks on the target server and issue alerts if the remaining space falls below the alert threshold.
• Windows Performance Monitoring: Monitor six performance indicators on the target server, including CPU, Memory, Disk I/O, Network I/O, and issue alerts when thresholds are exceeded.
• Custom Push Notification (API) Monitoring: Authenticate using a token and send the desired notification to NIMBUS Watch, which handles the push notification.
• SQL Server Transaction Log Size Monitoring: Monitor the size of transaction log files in SQL Server databases and set alert thresholds. Alerts are issued when thresholds are exceeded.
• SQL Server Job Schedule Monitoring: Monitor the SQL Agent jobs on the target SQL Server to check if they are disabled and whether the last run result was abnormal. Alerts are issued for such conditions.
• SQL Server Data Lock Monitoring: Monitor for data lock conditions in SQL Server databases and set thresholds. Alerts are issued when the lock duration exceeds the threshold.
• Execute SQL Command Monitoring: Monitor the target SQL Server by executing commands and checking if the returned results match predefined rules. Alerts are issued if they do not match.
• Windows Task Schedule Monitoring: Monitor the Windows task schedules on the target server to check for disabled tasks and abnormal last run results. Alerts are issued for such conditions.
• Advanced Windows Performance Monitoring: Monitor specific performance indicators on the target server, allowing customization of monitored objects (Category), instances (Instance), and counters (Counter). Alerts are issued when results do not meet user-defined success criteria.
• Advanced Windows Event Viewer Monitoring: Monitor specific events in the Event Log on the target server, including Windows logs and application and service logs. Alerts are issued when error events are detected.
• ODBC DSN Connection Monitoring: Monitor data sources configured in the ODBC Data Source Administrator on the target server (Windows). Alerts are issued when connections fail. If database commands and alert thresholds are set, the system connects to the data source database, executes the command, and issues alerts when response times exceed the threshold.
• Windows File Existence Time Monitoring: Monitor file folders on the target server. Alerts are issued when the creation date, modification date, or access date of files that meet the filter conditions, as set by the user during monitoring setup, exceed the alert threshold.
• Web Post Monitoring: Send requests via Http Post to the specified URL and receive the target website's response. Users can define success criteria, which the system uses to determine if the response meets the success conditions.
• Ceph OSD Daemon Monitoring: Monitor the status of the Ceph OSD Daemon on the target server (Linux). Alerts are issued when the status is abnormal.
• SNMP Disk Size Monitoring: Users can monitor the remaining space of a specific disk on the target server via Simple Network Management Protocol (SNMP). If the remaining space is below the alert threshold, an alert is issued.
• SNMP Performance Monitoring: Users can monitor the CPU and Memory performance indicators on the target server via Simple Network Management Protocol (SNMP). An alert is issued when the performance exceeds the alert threshold.
• SNMP Network Traffic Monitoring: Users can monitor the traffic of specific network interfaces on the target server via Simple Network Management Protocol (SNMP). An alert is issued when the network input or output traffic exceeds the alert threshold.
• IPMI Sensor Monitoring: Users can monitor the disk sensors and power supply sensors on the target server via Intelligent Platform Management Interface (IPMI). If the sensor results obtained during monitoring differ from the preset results, an alert is issued.
• IPMI OS Boot Monitoring: Users can monitor OS Boot events on the target server via Intelligent Platform Management Interface (IPMI). An alert is issued when there is an OS Boot event within the monitoring interval.
• Zabbix Alert Monitoring: Integrates the monitoring software Zabbix, allowing users to fetch alert information triggered by Zabbix according to the Zabbix host and permissions entered. The alerts are sent to users' mobile devices in real-time via NIMBUS Watch.
• MySQL Connection Monitoring: Users can monitor a specified database to check if it is operating normally. In addition to attempting to log in, it will also perform queries to ensure the database is indeed operating normally.
• MySQL Data Lock Monitoring: Users can monitor for data lock (Lock) conditions on the MySQL server and set a threshold. An alert is issued when the lock duration exceeds the threshold.
• MySQL Job Scheduler Monitoring: Users can monitor whether the Event on the target MySQL server is disabled. An alert is issued if it is disabled.
• MySQL Status Monitoring: Users can monitor the status of the target MySQL server to see if it meets the alert threshold. The status includes nine indicators: maximum connection ratio, rejected connection ratio, current connection ratio, InnoDB cache hit rate, Thread cache hit rate, locked connections, InnoDB redo logs ratio, full table scan ratio, and temporary table ratio. An alert is issued when the status does not meet the alert threshold.
• SMTP Monitoring: A mail sending test is conducted via Telnet command. It can be set to not actually send emails to avoid email accumulation. The SMTP server's response determines whether it is normal, and an alert is issued when an abnormality occurs.
• Grafana Alert Monitoring: Grafana is an open-source monitoring and analysis platform. NIMBUS Watch can fetch alert information from Grafana via the API provided by Grafana, and alert notifications are issued via NIMBUS Watch.
• cAdvisor Monitoring: cAdvisor is Google's open-source infrastructure monitoring tool. It runs on the Docker host to monitor the performance of containers. NIMBUS Watch periodically retrieves the performance of the monitoring target, and an alert notification is issued when it exceeds the threshold.
• Custom Push Message (Database) Monitoring: Users can enter custom query commands, and the results returned will be treated as information to be pushed. The results must include more than two columns, with the first column as the push message title and the second column as the push message content. Users can enter commands as needed. If there are too many records, only the first ten will be sent as alerts. Supported database connection methods include SQL Server, MySQL, and Oracle.
• Custom Push Message (ODBC) Monitoring: Users can enter custom query commands, and the results returned will be treated as information to be pushed. The results must include more than two columns, with the first column as the push message title and the second column as the push message content. Users can enter commands as needed. If there are too many records, only the first ten will be sent as alerts. The supported database connection method is ODBC.
• Custom Push Message (Text File) Monitoring: Users can enter a folder path. When the folder contains text files, the file capture interval is from the last monitoring execution time to the current monitoring execution time, based on the file modification time. The captured files will be treated as information to be pushed. During monitoring, the files to be alerted are copied to the monitoring module server for frontend viewing. The file name is the title during alerting, and a URL is provided to view the content. Only txt files smaller than 1MB are supported. Files larger than 1MB are not processed, and if there are too many files, only the latest ten are processed to avoid excessive alerts.
• Custom Push Message (Email) Monitoring: Users can enter email-related information, and NIMBUS Watch will read the email content according to the filter conditions, treating the email subject as the alert title and the email content as the alert content. If the number of emails retrieved within the monitoring interval exceeds ten, only ten will be sent to avoid excessive alerts. If the email contains private information, ensure that the alert recipient settings are correct.
• Web Test Monitoring: NIMBUS Watch can execute Selenium scripts. If the web test results are erroneous, it is considered abnormal, and an alert is issued. Currently, web test monitoring only supports executing Selenium scripts written in Python for Chrome tests. Before monitoring, please record the Selenium script and test it on the test machine using Python to execute the Selenium script.
• Oracle Connection Monitoring: Users can monitor a specified database to check if it is operating normally. In addition to attempting to log in, it will also perform queries to ensure the database is indeed operating normally.
• Oracle Datafiles Monitoring: Users can monitor specified datafiles. NIMBUS Watch provides three monitoring contents: average read time (ms), average write time (ms), and status. An alert is issued when the average read/write time exceeds the threshold or the status is offline.
• Oracle Tablespace Monitoring: Users can monitor specified tablespaces. NIMBUS Watch provides three monitoring contents: remaining space (MB), remaining space (%), and status. An alert is issued when the remaining space is below the threshold or the status is offline.
• Oracle Job Scheduler Monitoring: Users can monitor specified job schedules to see if they are disabled and if the execution results within the monitoring interval are abnormal. An alert is issued if any of the above conditions occur.
• Oracle Data Lock Monitoring: Users can monitor for data lock (Lock) conditions in the database and set a threshold. An alert is issued when the lock duration exceeds the threshold.
• Oracle Command Execution Monitoring: Users can monitor the target database by entering commands to determine if the returned number of records meets the preset rules. An alert is issued if the rules are not met.
• UNC Path Connection Monitoring: Users can test the connection to the UNC path via this monitoring. An alert is issued if the connection fails.

Stay informed anytime, handle issues promptly.

• Dual APP Design: Dual versions for public cloud and private cloud, catering to various types of needs.
• Two Login Mechanisms: The public cloud integrates Facebook, Google, CAMP, and Weibo accounts, covering the most popular login mechanisms. The private cloud version allows login via local accounts or AD accounts. Local accounts are based on the local accounts of the host where the private monitoring module is installed, allowing login to the NIMBUS Watch private cloud version as long as the host's local account can log in. AD accounts integrate with the company's AD Domain authentication method, eliminating the need to maintain a separate personnel list.
• Forty-six Monitoring Items: Covers basic monitoring modules, SQL Server 2014 monitoring module, Windows Server 2012R2 monitoring module, MySQL monitoring module, Container monitoring module, advanced monitoring module, and Oracle monitoring module.
• Flexible Monitoring Rule Settings: Allows users to set monitoring rules as needed, operating 24/7.
• Flexible Alert Rule Settings: Currently provides mechanisms for email and message push notifications, with phone call notifications to be offered in the future.
• Convenient Setup: Can be operated via mobile devices, allowing monitoring status to be managed anytime, anywhere.
• Custom Parameter Settings: The private cloud version allows users to adjust various monitoring parameters based on the scale of monitoring.

Benefits After Implementation

• Low cost, immediate installation, and immediate use.
• Stay informed and handle issues promptly.
• Shorten problem resolution time.
• Automated Processing (Windows Services/IIS Application Pool can be set to start automatically).
• Utilize manpower and time for more productive and contributive tasks.
• Achieve comprehensive database monitoring for SQL Server connections, transaction logs, job scheduling, and data locking.
• Monitor host performance, hard disk size, and tasks to prevent unexpected host failures leading to service interruptions.