What kinds of DB2, Oracle, and SQL Server backup alarms are there? (4294821)

Customer is often getting alarms from Foglight concerning our databases (Oracle and SQL Server) backups

Example:
Foglight Cartridge for Oracle has generated a Warning alarm for Oracle instance MYSERVER.DOMAIN.COM-MYINSTANCE on host MYSERVER.DOMAIN.COM.
Alarm: DBO - Backup Job Failure (alarm group: Storage)
Severity: Warning
Message: The backup job: ARCHIVELOG started at: Tue Jun 05 23:37:11 EDT 2012 and failed.
Created on: Wed Jun 06 02:06:02 EDT 2012

When checking with our backup tool Data Protector that uses RMAN scripts for the Oracle backup, we can see that the backup was successful

What does foglight check to trigger the backup alarms for oracle and sql server?
What are the differences between the different alarms?

Is DB2 backup monitoring available?

We have two Oracle alarms regarding backup jobs, both alarms are based on information retrieved.

1). Backup Job Failure - fires on any backup job failure
This alarm is invoked when the Oracle Recovery Manager (RMAN) backup job has ended with one of the following statuses:
• FAILED
• COMPLETED WITH ERRORS
• COMPLETED WITH WARNINGS

The query pulls information in the monitored database from SYS.V_$RMAN_STATUS for the "Backup" operation.

2). Days since full backup - fires when the number of days the last full backup was completed successfully exceeds the predefined threshold.
This alarm is invoked when the number of days that elapsed since the last successful backup via the Oracle Recovery Manager (RMAN) exceeds a predefined registry variable value.

For SQL Server we have the following alarms:

1. Days Since Last Backup - This alarm is invoked when the number of days that have elapsed since the last database backup exceeds a predefined registry variable value.
2. Days Since Last Backup - No Backup: This alarm is invoked when the database has never been backed up.

DB2 backups will be added in a future release of the Foglight for DB2 cartridge.

For the Oracle "DBO - Backup Job Failure" alarm, currently if the RMAN output contains the word WARNING in its message, the agent ends up setting the backup status metric to "Complete with warnings":

As an example: "RMAN-08137: WARNING: archive log not deleted as it is still needed"

Enhancement request ODB-5995 has been submitted to add the ability to exclude certain statuses from the alarm trigger in the "DBO - Backup Job Failure" rule