SLA and performance tracking can be managed in Qorus with service calls and job execution through configuration (i.e. without requiring any development) and arbitrarily with any part of the system by using the SLA API.

SLA events can be tracked once an SLA has been created; SLA events are flushed to the system database asynchronously in another thread of execution from the associated action in order to avoid causing a performance penalty in the action itself.

The following system options affect the SLA event cache:

sla-max-events: the maximum number of SLA events to store before flushing to the database
sla-max-sync-secs: the maximum number of seconds to hold SLA events before flushing to ORDER_INSTANCE_KEYS

Qorus will flush SLA events to disk when either the maximum time or the maximum cache size is reached, whichever comes first.

This means that the sla-max-sync-secs option determines the maximum delay an SLA event can remain in the cache.

The following REST API URI paths can be used to manage and report SLAs:

/api/v2/slas system SLA information
/api/v2/slas/{sla} actions on an existing SLA