View Source

The Database Agent sends the database events to the Controller when the agent detects issues with database connection, failover, or database replication. You can view the details of the events on the Databases > Events page. This page displays the event summary, triggered time, and database type.

You can view the following information in the detailed view:

Summary: Displays the details of the event
Details: Displays the properties of the event.
Actions Executed: Displays the executed actions if you have created a policy.

If you do not want the Database Agent to send database events to the Controller, then set the dbagent.event.trigger.enabled property to false at the agent level. This property is enabled by default.

The following table lists the custom database events with the supported database:

Event	Database
`FAILOVER`	SQL Server PostgreSQL Oracle MySQL
`DB_CONNECTION_DOWN`	All database types supported by Database Agent. See Database Visibility Supported Environments.
`DB_CONNECTION_UP`	All database types supported by Database Agent. See Database Visibility Supported Environments.
`REPLICATION_FAILURE`	PostgreSQL
`BLOCKING_SESSION`	SQL Server Oracle
DAYS_SINCE_FULL_BACKUP	Oracle
DAYS_SINCE_FULL_BACKUP_PDB	Oracle
HOURS_LOG_BACKUP	Oracle
BACKUP_SUCCESSFUL	Oracle
BACKUP_FAILED	Oracle

Database Agent supports the following Oracle database architectures:

Container Database (CDB) >=12.2
Non-container Database (non-CDB)
Real Application Cluster (RAC)

Database Agent uses the data generated by Oracle Recovery Manager (RMAN) to trigger backup events.

To enable or disable the Oracle Backup and Blocking Session events, navigate to Controller Settings > Controller Configurations and change the value of the following properties to true or false:

dbagent.oracle.backup.events.enabled
dbagent.oracle.blocking.session.event.enabled

You can configure alert policies with the custom database events. See Configure Policies.

Failover

Description: This event is sent to the Controller when the primary node fails.

Database Type	Summary
Oracle	Failover occurred in `<database-type>, <collector-name> - <database-collector-name>` RAC cluster
PostgreSQL SQL Server MySQL	Failover occurred for `<database-type>`, database instance `<database-instance-name>`

Severity: Error

Custom Event Type: FAILOVER

While configuring alert policies, you can use the Custom Events panel to add a custom event filter.

Click + and specify the custom event type.

Filter the events by using a combination of the following properties:

Property	Applicable Database	Description
`availabilityGroupName`	SQL Server	Availability group name of the cluster
`failedNode`	PostgreSQL Oracle MySQL	Name of the failed node
`failedAgName`	SQL Server	Name of the failed availability group
`failedReplicaHostName`	SQL Server	Name of the failed replica hostname
`failedReplicaID`	SQL Server	Failed replica ID
`port`	SQL Server PostgreSQL Oracle MySQL	Port of the node or failed node
`dbCollectorName`	SQL Server PostgreSQL Oracle MySQL	Name of the database collector
`databaseType`	SQL Server PostgreSQL Oracle MySQL	Database type
`primaryNodesAfterFailover`	PostgreSQL Oracle MySQL	Current primary nodes after failover
`timeStamp`	SQL Server PostgreSQL Oracle MySQL	Time at which the event is triggered

Database Connection Down

Description: This event is sent to the Controller when the collector cannot establish a connection with the database or if an existing connection fails. For a cluster, each node failure is sent as a separate event. This event is reported at an exponential time gap: 2, 4, 8, 16, 32 minutes, and so on for 24 hours. Then, the event is reported every 24 hours.

Node	Summary
Single	Connection failure in `<database-type>, <database-collector-name, collector-name>`
Cluster	Connection failure in `<database-instance-name: node-name>`

Severity: Error

Custom Event Type: DB_CONNECTION_DOWN

While configuring alert policies, you can use the Custom Events panel to add a custom event filter.

Click + and specify the custom event type.
Filter the events by using a combination of the following properties:
Property Description
dbCollectorName Name of the database collector
nodeName Name of the node
databaseType Database type
timeStamp Time at which the event is triggered
port Port of the node

Database Connection Up

Description: This event is sent to the Controller when databases get connected after the DB_CONNECTION_DOWN event is triggered.

Severity: Info

Custom Event Type: DB_CONNECTION_UP

While configuring alert policies, you can use the Custom Events panel to add a custom event filter.

Click + and specify the custom event type.
Filter the events by using a combination of the following properties:
Property Description
dbCollectorName Name of the database collector
nodeName Name of the node
databaseType Database type
timeStamp Time at which the event is triggered
port Port of the node

Replication Failure

Description: This event is sent to the Controller when the status property in the pg_stat_replication table changes to stopping or failed.

Summary: Replication failure occurred for database instance - <database-instance-name>, <database-type>

Severity: Error

Custom Event Type: REPLICATION_FAILURE

While configuring alert policies, you can use the Custom Events panel to add a custom event filter.

Click + and specify the custom event type.

Filter the events by using a combination of the following properties:

Property	Description
`confl_bufferpin`	Represents the number of times there was a conflict related to buffer pinning. Buffer pin conflicts occur when multiple transactions attempt to access the same buffer (cache page) concurrently.
`confl_deadlock`	Represents the number of times a deadlock situation was detected in the database. A deadlock occurs when two or more transactions are waiting for each other to release locks, resulting in a circular dependency.
`confl_lock`	Represents the number of times there was a conflict related to locking. Lock conflicts occur when one transaction attempts to acquire a lock that is already held by another transaction.
`confl_snapshot`	Represents the number of times there was a conflict related to concurrent snapshots. A snapshot conflict occurs when a transaction tries to access a row while another transaction is updating or deleting the same row.
`confl_tablespace`	Represents the number of times there was a conflict related to tablespace allocation. A tablespace conflict occurs when multiple transactions try to allocate space in the same tablespace concurrently.
`conninfo`	The connection string used by the WAL receiver process to connect to the primary server.
`databaseType`	Database type
`dbCollectorName`	Name of the database collector
`failedApplicationNode`	Represents the replication slot name used by the WAL receiver process, if applicable. Replication slots are used to track the progress of replication.
`failedNode`	Name of the node
`last_msg_receipt_time`	Indicates the timestamp of the last message received by the standby server from the master server
`last_msg_send_time`	Indicates the timestamp of the last message sent from the master server to the standby server
`latest_end_lsn`	Indicates the LSN of the most recent completed WAL record on the standby server. It represents the end of the last applied transaction.
`latest_end_time`	Indicates the timestamp of the most recent completed transaction on the standby server.
`port`	Port of the node
`reason`	Reason for the failure
`status`	Indicates the current status of the WAL receiver process. The possible values include: `stopped`: The WAL receiver is stopped `streaming`: The WAL receiver is actively streaming WAL data from the master server
`timeStamp`	Time at which the event is triggered

Blocking Session

Description: This event is sent to the Controller when there is a session that is blocked by another session.

Severity: Error

Custom Event Type: BLOCKING_SESSION

While configuring alert policies, you can use the Custom Events panel to add a custom event filter.

Click + and specify the custom event type.

Filter the events by using a combination of the following properties:

Property	Description
`blockedObject`	The object that is blocked
`blockedSessionId`	ID of the session that is blocked
`blockedSqlStatement`	Blocked query text
`blockedSqlStatementHash`	Hash of the blocked query text
`blockingSessionId`	ID of the session that is blocking the session
`blockingSqlStatementHash`	Hash of the blocking query text
`databaseType`	Database type
`dbCollectorName`	Name of the database collector
`dbInstanceName`	Name of the database instance
`duration (hh:mm:ss)`	Duration for which the session is blocked
`eventRuleName`	Name of the event rule
`eventType`	Name of the reported event
`timeStamp`	Time at which the event is triggered
`violationID`	Unique ID of the violation

Days Since Full Backup

Description: This event is sent to the Controller when the specified number of days has passed since the last backup.

Severity: You can set the severity to the following severity types:

Type	Description
Warning	Set the warning threshold in days.
Critical	Set the critical threshold in days.

Custom Event Type: DAYS_SINCE_FULL_BACKUP

While configuring alert policies, you can use the Custom Events panel to add a custom event filter.

Click + and specify the custom event type.

Filter the events by using a combination of the following properties:

Property	Description
`databaseName`	Name of the database
`dbCollectorName`	Name of the database collector
`containerID`	Unique ID of the container in a multitenant container database (CDB)
`containerPDBName`	Name of the pluggable database (PDB)
`eventRuleName`	Name of the event rule
`lastBackupTimeStamp`	Time at which the last backup was taken
`nodeName`	Name of the node
`timeStamp`	Time at which the event is triggered
`userName`	User name
`violationID`	Unique ID of the violation

Days Since Full Backup (PDB)

Description: This event is sent to the Controller when the specified number of days has passed since the last full backup of the Oracle pluggable database (PDB). This event does not consider the multitenant container database (CDB) and root.

Severity: You can set the severity to the following severity types:

Type	Description
Warning	Set the warning threshold in days.
Critical	Set the critical threshold in days.

Custom Event Type: DAYS_SINCE_FULL_BACKUP_PDB

While configuring alert policies, you can use the Custom Events panel to add a custom event filter.

Click + and specify the custom event type.

Filter the events by using a combination of the following properties:

Property	Description
`databaseName`	Name of the database
`dbCollectorName`	Name of the database collector
`containerID`	Unique ID of the container in a multitenant container database (CDB)
`containerPDBName`	Name of the pluggable database (PDB)
`eventRuleName`	Name of the event rule
`lastBackupTimeStamp`	Time at which the last backup was taken
`nodeName`	Name of the node
`timeStamp`	Time at which the event is triggered
`userName`	User name
`violationID`	Unique ID of the violation

Hours Since Last Redo Log Backup

Description: This event is sent to the Controller when the specified number of hours has passed since the backup was redone. This event considers only the multitenant container database (CDB) and non-CDB databases.

Severity: You can set the severity to the following severity types:

Type	Description
Warning	Set the warning threshold in hours.
Critical	Set the critical threshold in hours.

Custom Event Type: HOURS_LOG_BACKUP

While configuring alert policies, you can use the Custom Events panel to add a custom event filter.

Click + and specify the custom event type.

Filter the events by using a combination of the following properties:

Property	Description
`databaseName`	Name of the database
`dbCollectorName`	Name of the database collector
`eventRuleName`	Name of the event rule
`lastBackupTimeStamp`	Time at which the last backup was taken
`nodeName`	Name of the node
`timeStamp`	Time at which the event is triggered
`userName`	User name
`violationID`	Unique ID of the violation

Backup Successful

Description: This event is sent to the Controller when the backup is complete for CBD, non-CBD, and PDB Oracle databases.

Severity: Info

Custom Event Type: BACKUP_SUCCESSFUL

While configuring alert policies, you can use the Custom Events panel to add a custom event filter.

Click + and specify the custom event type.

Filter the events by using a combination of the following properties:

Property	Description
`databaseName`	Name of the database
`dbCollectorName`	Name of the database collector
`containerID`	Unique ID of the container in a multitenant container database (CDB)
`containerPDBName`	Name of the pluggable database (PDB)
`eventRuleName`	Name of the event rule
`eventType`	Name of the reported event
`lastBackupTimeStamp`	Time at which the last backup was taken
`nodeName`	Name of the node
`timeStamp`	Time at which the event is triggered
`userName`	User name
`violationID`	Unique ID of the violation

Backup Failed

Description: This event is sent to the Controller when the backup fails for CBD, non-CBD, and PDB databases. This event is supported for Oracle Database >=19c.

Severity: Info

Custom Event Type: BACKUP_FAILED

While configuring alert policies, you can use the Custom Events panel to add a custom event filter.

Click + and specify the custom event type.

Filter the events by using a combination of the following properties:

Property	Description
`databaseName`	Name of the database
`dbCollectorName`	Name of the database collector
`containerID`	Unique ID of the container in a multitenant container database (CDB)
`containerPDBName`	Name of the pluggable database (PDB)
`eventRuleName`	Name of the event rule
`eventType`	Name of the reported event
`lastBackupTimeStamp`	Time at which the last backup was taken
`nodeName`	Name of the node
`timeStamp`	Time at which the event is triggered
`violationID`	Unique ID of the violation