Good availability reporting
How about on developing good availability reports:
- Service Tree definition (composed of triggers)
- SLA definition over service trees (not IT services based)
- Outage period SLA breakage justification for exclusion
- Good SLA account
- Generating PDF reports (from templates)
We'd be willing to contribut€ to make this happen.
IT Services's output doesn't seem to give an accurate output on both availability and number of "outages". Also it's not true multi-tenant (the empty trees will show even to users without access to any of the triggers under it).
We'd want something trustable where we could build a logical tree of dependencies, and with event data plus, taking into account maintenance periods and some manual SLA breakage justification, would generate availability data for periods (week, month, year) and match that against defined minimum SLAs, reporting over it and generating PDF from template.
- Service Tree definition (composed of triggers)
- SLA definition over service trees (not IT services based)
- Outage period SLA breakage justification for exclusion
- Good SLA account
- Generating PDF reports (from templates)
We'd be willing to contribut€ to make this happen.
IT Services's output doesn't seem to give an accurate output on both availability and number of "outages". Also it's not true multi-tenant (the empty trees will show even to users without access to any of the triggers under it).
We'd want something trustable where we could build a logical tree of dependencies, and with event data plus, taking into account maintenance periods and some manual SLA breakage justification, would generate availability data for periods (week, month, year) and match that against defined minimum SLAs, reporting over it and generating PDF from template.
Comment