Filtering by Job Category in the "DBSS - Jobs Failed" alarm is not dynamic (4372796)

Filtering by Job Category in the "DBSS - Jobs Failed" alarm is not dynamic

The Rule Filters panel in the "DBSS-Jobs Failed" alarm configuration is being used to exclude jobs under a specific category. A category is selected to choose all of the jobs in the category when the rule is configured, and then the configuration is saved.

At a later time, additional jobs are added in SQL Server to the category but the alarm exclusions do not include newer jobs in the exclusion list.

Is it possible for the exclusion list to dynamically add new jobs in the previously applied category to the exclusions?

-----

Scenario

1. "FailedJob1", "FailedJob2", and "FailedJob3" are members of the "[Uncategorized (Local)]" category in SQL Server
2. A "DBSS - Jobs Failed" exclusion is added for the "[Uncategorized (Local)]" category in a database agent
3. Later, "FailedJob1" is created in SQL Server in the "[Uncategorized (Local)]" category but this is not automatically added to the exclusions on the basis of the category.

The Rule Exceptions in the "DBSS - Jobs Failed" alarm are used to maintain exceptions based on job names only rather than by setting exclusions by category. The category option is provided for ease of initial configuration and adding multiple jobs which can be added or deleted prior to saving the changes.

NOTE: After the category has been applied in the rule exclusions, all of the jobs belonging to that category are added to the exclusion list. The user then has the opportunity to add or delete jobs (including those from the category just applied) from the exclusion list.

WORKAROUND

Add a rule exception using a Registry Expression (regex) to include new jobs that match an existing pattern. For example:

1. An Exception Value called "FailedJob.*" is added to match the jobs "FailedJob1", "FailedJob2", and "FailedJob3" when the rule exceptions are first applied.
2. Later, if a new job "FailedJob4" is added into SQL Server. This job name will be included in the existing exception because the job name already matches the regular expression previously configured.

STATUS

Enhancement Request FGSS-I-168 has been logged for the "DBSS - Jobs Failed" rule to filter job alarms by category so that new jobs added to the instance will also be included in existing exclusions. This will be review by Product Management for consideration of inclusion in a future release of Foglight.

 

 

FGSS-I-168