Aborted clients |
Checks the number of clients not closing the connection properly. |
Aborted clients |
Checks the number of clients not closing the connection properly. |
Aborted connections |
Checks the number of aborted client connections. |
Aborted connections |
Checks the number of aborted client connections. |
DBMS uptime |
Collects uptime statistics for the MariaDB instance. |
Aborted connects alert |
Collects uptime statistics for the MariaDB instance. |
Maximum connections alert |
Collects uptime statistics for the MariaDB instance. |
Aborted clients |
Checks the number of clients not closing the connection properly. |
Aborted clients |
Checks the number of clients not closing the connection properly. |
Aborted connections |
Checks the number of aborted client connections. |
Aborted connections |
Checks the number of aborted client connections. |
DBMS uptime |
Collects uptime statistics for the MySQL instance. |
DBMS uptime |
Collects uptime statistics for the MySQL instance. |
DBMS uptime |
Collects uptime statistics for the MySQL instance. |
Aborted connects alert |
Collects uptime statistics for the MySQL instance. |
Maximum connections alert |
Collects uptime statistics for the MySQL instance. |
MySQLd process alert |
Collects uptime statistics for the MySQL instance. |
Alert log check |
This check reads and looks for errors in the database alert log. |
Alert log check |
This check reads and looks for errors in the database alert log. |
Alert log check |
This check reads and looks for errors in the database alert log. |
Alert log check |
This check reads and looks for errors in the database alert log. |
Alert log check |
This check reads and looks for errors in the database alert log. Uses embedded java to read files. |
Alert log check |
This check reads and looks for errors in the database alert log. Uses embedded java to read files. |
Archive status Check |
Checks how many redolog files that are not archived. |
Backup log Check 10g |
Checks for errors in a log file (e.i. backup log). For backups not using RMAN. |
Backup log Check 8i |
Checks for errors in a log file (e.i. backup log). For backups not using RMAN. |
Backup log Check 9i |
Checks for errors in a log file (e.i. backup log). For backups not using RMAN. |
Data Guard Archive Status |
Checks that the standby database is receiving archive files from master database. |
Data Guard Archive Status Check |
Checks that the standby database is receiving archive files from master database. |
Database link check |
Checks database links. |
Instance alert log |
Reads and checks errors in the V$DIAG_ALERT_EXT performance view contained in the XML decoded version of the XML version of Alert log file. |
Database uptime |
Collects database uptime statistics for all instances mounted on the database. |
Dba Jobs check |
Detecting failed scheduled jobs in old style dba_jobs. |
DBMS uptime |
Collects uptime statistics in database. |
Export log Check |
Checks for errors in a log file (i.e. export log). |
File status check |
Reacts on any changes in status of data files and/or temporary files. |
Job scheduling check |
Detecting failed scheduled jobs. The STATUS column in the Oracle dictionary view DBA_SCHEDULER_JOB_RUN_DETAILS is used to detect scheduled jobs that have failed. |
Listener log check |
This checks and reads errors from the database listener log. Using Oracle native code to read. |
Listener log check |
This checks and reads errors from the database listener log. Using Oracle native code to read. |
Listener log check |
This checks and reads errors from the database listener log. Using Oracle native code to read. |
Listener log check |
This checks and reads errors from the database listener log. Using Oracle native code to read. |
Listener log check |
This checks and reads errors from the database listener log. Using Oracle native code to read. |
Listener log check |
This checks and reads errors in database listener log. Using embedded java to read. |
Listener log check |
This checks and reads errors in database listener log. Using embedded java to read. |
Listener status check |
Checks listener status to verify if up and running, requires java support in the database. |
Max datafiles check |
Checks the ‘soft limit’ and the ‘hard limit’ of the maximum number of physical OS files, that can be mapped to an Oracle instance. |
Database mount state |
Checks the ‘soft limit’ and the ‘hard limit’ of the maximum number of physical OS files, that can be mapped to an Oracle instance. |
Datafile status |
Checks the ‘soft limit’ and the ‘hard limit’ of the maximum number of physical OS files, that can be mapped to an Oracle instance. |
Max datafiles |
Checks the ‘soft limit’ and the ‘hard limit’ of the maximum number of physical OS files, that can be mapped to an Oracle instance. |
RMAN ARCHIVELOG backup status alert |
Checks the ‘soft limit’ and the ‘hard limit’ of the maximum number of physical OS files, that can be mapped to an Oracle instance. |
RMAN backup status alert |
Checks the ‘soft limit’ and the ‘hard limit’ of the maximum number of physical OS files, that can be mapped to an Oracle instance. |
Password expire |
Checks for users whose password will soon expire. |
PDB status |
Alerts if PDB is not in correct state |
RMAN backup status |
Checks the status of RMAN backup from V$RMAN_BACKUP_JOB_DETAILS performance view. |
RMAN backup status |
Checks the status of RMAN backup from V$RMAN_BACKUP_JOB_DETAILS performance view. |
RMAN backup status |
Checks the status of RMAN backup from V$RMAN_BACKUP_JOB_DETAILS performance view. |
RMAN backup status |
Checks status of RMAN backup from V$RMAN_BACKUP_JOB_DETAILS performance view. |
RMAN backup status |
Checks the status of RMAN backup from V$RMAN_BACKUP_JOB_DETAILS performance view. |
RMAN archivelog backup status |
Checks the status of RMAN archivelog backup from V$RMAN_BACKUP_JOB_DETAILS performance view. |
RMAN backup status |
Checks the status of RMAN full backup from V$RMAN_BACKUP_JOB_DETAILS performance view for input_type ‘DB FULL‘. The procedure can also check incremental (input_type ‘DB INCR‘) level 0 backup (equivalent to full backup) by checking V$BACKUP_DATAFILE performance view (column INCREMENTAL_LEVEL=0). |
RMAN incremental backup status |
Checks the status of RMAN incremental backup (input_type ‘DB INCR‘) from V$RMAN_BACKUP_JOB_DETAILS performance view. |
RMAN recovery area backup status |
Checks the status of RMAN recovery area backup (input_type ‘RECVR AREA‘) from V$RMAN_BACKUP_JOB_DETAILS performance view. |
Tablespace in BEGIN BACKUP mode |
Checks if any of the tablespaces are in ‘BEGIN BACKUP‘ mode (caused by DDL ‘alter tablespace |
Test alert db |
Test alert that alerts every ‘X’ minutes. |
Test alert |
Test alert that alerts every ‘X’ minutes. |
TNSping check |
Checks TNSping connectivity on listed targets. Task requires ‘java’ support. Supports Linux/Unix and Windows, will react with an alarm if host is unreachable. |
Backup check – pg_dump |
Checks that there exists an up to date backup file. |
Backup check – WAL |
Checks that the WAL files have been backed up. |
DBMS uptime |
Collects database uptime statistics. |
dbWatch engine alert |
Collects database uptime statistics. |
Agent error log |
Reads and checks the Agent error log file by using the sp_readerrorlog stored procedure. |
Agent Jobs Check |
Checks whether there exists jobs on the SQL server which have not been executed, or have failed during execution. |
Agent Jobs Check |
Checks whether there exists jobs on the SQL server which have not been executed or have failed during execution. |
SQL Server Agent status |
Checks if the SQL Server Agent is running. |
Database backup |
This procedure analyzed the backup statistics from msdb.dbo.backupset table (excluding system databases: master, model and msdb). |
Database backup |
This procedure analyzed the system database backups statistics from msdb.dbo.backupset table. |
Database backup |
This procedure analyzes the backup statistics (type D and I) from the msdb.dbo.backupset table (excluding the system databases: master, model and msdb). |
Database Log backup |
This procedure checks the database transaction log backups from the msdb.dbo.backupset table (excluding system databases: master, model and msdb). |
Database backup |
This procedure analyzes the backup statistics (type D and I) from the msdb.dbo.backupset table (excluding the system databases: master, model and msdb). |
Database backup |
This procedure analyzes the backup statistics (type D) from the msdb.dbo.backupset table for databases in SIMPLE recovery model (excluding the system databases: master, model and msdb). |
Database backup |
This procedure analyzes the FULL backup statistics for the system databases (master, model and msdb) using data from the msdb.dbo.backupset table. |
Database Log backup |
This procedure checks the database transaction log backups from the msdb.dbo.backupset table (excluding system databases: master, model and msdb). |
Collation check |
Checks if there is a collation conflict with temp tables and table variables. |
Check database recovery mode |
Checks if all databases are running in FULL or SIMPLE recovery mode. |
Database status |
Checks if all databases have status ONLINE |
Database status |
Checks if all databases have status ONLINE |
Database Server uptime |
Collects database server uptime statistics. |
Database Server uptime |
Collects database server uptime statistics. |
Database Server uptime |
Collects database server uptime statistics. |
Deadlocks event collector |
Collects deadlocks event statistics from Microsoft SQL Server Extended Event Log files. If configured a warning or an alarm can be triggered when a deadlock is detected. |
Instance error log |
Reads and checks the Instance error log file by using the sp_readerrorlog stored procedure. |
Instance error log |
Reads and checks the Instance error log file by using the AWS rdsadmin.dbo.rds_read_error_log stored procedure. |
Instance status |
This alert checks if the instance has been restarted since the last check |
Database backup |
This alert checks if the instance has been restarted since the last check |
Database log backup |
This alert checks if the instance has been restarted since the last check |
Database status |
This alert checks if the instance has been restarted since the last check |
Missing database backup |
This alert checks if the instance has been restarted since the last check |
Missing database log backup |
This alert checks if the instance has been restarted since the last check |
Program status |
Checks for any program connected to the SQL Server by checking the program_name column in the master.dbo.sysprocesses table. |
Report Server status |
Checks if the program ‘Report Server’ is connected to the SQL Server by checking the program_name column in the master.dbo.sysprocesses table. |
Restricted Enterprise edition features |
Checks if there are any restricted features in use (supported only by Enterprise or Developer SQL Server edition). |
Restricted Enterprise edition features |
Checks if there are any restricted features in use (supported only by Enterprise or Developer SQL Server edition). |
Restricted Enterprise edition features 2005 |
Checks if there are any restricted features in use (supported only by Enterprise or Developer SQL Server edition). |
Test alert |
Test alert that alerts every ‘X’ minutes. |
Database backup |
Checks backup status of all databases. |
Database status |
Checks status of all databases defined on the system. The following incidents triggers a warning or an alarm: |
DBMS uptime |
Collects database uptime statistics. |