Availability Report

Registered by Laercio

Availability Report

As a system that provides service, I believe that this functionality is very interesting and low complexity.

Displays in the menu, we could have an Availability Report.
The Displays the user has access to, we could present the OffLine events, duration,%% available and unavailable, so calculating the SLA of Displays.

EX: 99.00% availability (Online) / 10% Unavailability (OffLine)

The Script maintenance could feed these records, stating when a machine is offline generating a record in the report, and telling you when you are online again entering this information in the report.

Basically a timeline of events, online and offline, with calculations based on an availability calendar. Select start date and end date, and displays or displays all the User has at least read access.

What do you think?

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Laercio
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon 1.7.0-alpha2
Started by
Dan Garner
Completed by
Dan Garner

Related branches

Sprints

Whiteboard

Maintenance Event History Report.

DG: We need to get some more clarity on exactly what is required here. There are two ideas that come to my mind for possible solutions:

1. A log of downtime events. When a client goes "down" a record is created with a fromDT of the last accessed date. When a client comes "up" the record is closed off with a toDT of "now".

2. A log of maintenance events. Log all maintenance events, email, log tidy, stats tidy, etc.

Option 1 has the advantage of lending itself to a very "easy to understand" report with a from date, to date and duration of downtime.

Option 2 has the advantage of being more inclusive of all events that are occurring and acts as a history log of the maintenance.

An alternative is that these are actually separate blueprints.

Thoughts??...

(?)

Work Items

Work items:
Decide on Spec (decided on option 1): DONE
Develop: DONE

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.