SLA Violations - sonata-nfv/tng-sla-mgmt GitHub Wiki

Monitoring plays an important role in determining whether an SLA has been violated. Monitoring SLA violations begins once an SLA has been defined, during the successful NS instantiation process. The SLA Manager sends additional (optional) monitoring metrics based on the selected SLA on order to be measured in a defined time window.
Monitoring can be used to detect whether an SLA has been violated, and if so the Monitoring Manager informs the SLA Manager about which metric was exceeded with an alert.

The SLA Mananger is responsible to keep track of all SLA violations, and store them into it;s internal PostgreDB - in the table violations. Specifically keeps track of which SLA was violated, with which Network Service Instance is linked, and of course the customer details who instantiated this service.

Once a SLA is violated, it is worth mentioning that is no longer active (it's status becomes violated), and can be deleted any time by the operator.