Severity Thresholds - assure_dq - Latest

Assure DQ Administrative Console

Product type
Software
Portfolio
Verify
Product family
Assure
Product
Assure DQ
Version
Latest
ft:locale
en-US
Product name
Assure DQ, ER, Insight and Perceive
ft:title
Assure DQ Administrative Console
Copyright
2025
First publish date
2005
ft:lastEdition
2025-11-28
ft:lastPublication
2025-11-28T07:19:50.245000
L1_Product_Gateway
Verify
L2_Product_Segment
Data Quality
L3_Product_Brand
Precisely Infogix
L4_Investment_Segment
Legacy Infogix DQ
L5_Product_Group
Legacy Infogix DQ
L6_Product_Name
Product Feature
Assure DQ

Severity thresholds are assigned at both the category and log output level.

Severity thresholds are hierarchical, and the severity level includes messages of the specified level and all lower-level messages.

For example, you assign a severity threshold of Fatal to the category and select Alarm as the log output. If the severity level assigned to Alarm is Debug, the system will not log messages higher than Debug.

However, you can assign a severity level to a category that will filter the severity level assigned to the log output. In the scenario described above, if Alarm has a severity threshold of Fatal, choosing Debug at the category level will filter out any log messages higher than Debug.

The following table shows the highest level message logged by each severity threshold:

Severity Threshold Description
Fatal Only fatal error messages are logged.
Error Fatal and error messages are logged.
Warning Fatal, error, and warning messages are logged.
Info Fatal, error, warning, and informational messages are logged.
Debug All messages, including debug messages, are logged.
Tip: The severity level assigned at the log output level is DEBUG; this threshold can be overridden only for a rolling file appender.