On 8/31/2018 at 4:25 AM, Mosh said:In the real world, in every organisation that I've worked in, there has been a requirement to retrospectively adjust SLAs as sometimes root cause analysis can take weeks or months in complex environments.
Rather than tweak SDT, could we have another type of entry that we could apply in a very similar fashion, and would be taken into account by the SLA algorithm in the same way it takes SDTs into account?
Totally agree Mosh. We want to use LM as a business reporting tool, but it's extraordinarily labor intensive to export all of the outage events, remove errornous entries and recalculate the SLA for each service, each month. Another type of entry (EDT - explained/excluded downtime) to apply retrospectively such that pulling SLA data at EOM results in business-accurate data being returned through the built in LM API/dashboards/custom reporting, rather than recalculating everything manually.
