The order of precedence for logging and notification by IDMDF is determined by custom system properties, predefined SLA values, and a default SLA value for all events.

1. Oracle Identity Governance lets you set the SLA value for an operation or event. You can do that by defining a system property with keyword in the format IDMDF:EVENT_NAME, and specifying an appropriate value. You can determine the event name by referring to a list of predefined event APIs and corresponding SLA values, as listed in SLA for Predefined Operations.

   For example, for the search catalog event, specify a keyword IDMDF.Search.Catalog for the system property you create with value as 50000 (in milliseconds). Here, the predefined event API name is Search Catalog-API. The value you specify for the system property will override the predefined SLA value, which is 60000 milliseconds. Therefore, if the search catalog operation takes more that 50000 milliseconds to complete, then a notification is sent to the administrator with diagnostic information.

   Note:

   See unresolvable-reference.html#GUID-16B4158A-A6AF-4645-A15E-32CB708546D8 for information about creating system properties.

   See Understanding the Output for information about the output of IDMDF and the mail format in which notification is sent.

   If a property is defined for the event and an appropriate value is set for that, then IDMDF uses that to log and send notification.
2. If you do not define a system property for the event, then the default SLA value for that event API is considered by IDMDF for SLA monitoring and sending notification.
3. If the SLA value is not predefined for an event, then the SLA value for that event is determined by the IDMDF: Default SLA system property. See Default System Properties in Oracle Identity Governance for information about the IDMDF: Default SLA system property.