User Sleep Retrospective

This release includes a new optional feature to display a retrospective of an operator's sleep loss across past on-call rotations!

Notes:

• Via the global config option oncall_sleep_retrospective_count, users can view the past few rotations' impact on their sleep.
• The retrospective provides the same information that's available in the on-call report visible to all users.
• The goal of this update is to help measure (on the dimension of sleep, at least) just how good/bad past rotations have been.

Other updates:

• Added support for Github Enterprise thanks to @ematthews.
• Minor CSS bug fix thanks to @russtaylor.

Hide Events (aka Soft Deletes)

Hide Events

In v0.2 one can hide events in the on-call report. This is useful in cases where the on-call provider returns duplicate events or multiple events fired for a single alert due to an unforeseen issue (think Nagios messages being queued by an MTA) as in the example below:

Hiding and Toggling Events

To hide an event in the on-call report, click the Hide Event? checkbox and save the report. If you later determine that the event should be visible, go back to the on-call report and click the Toggle Hidden Events button to display hidden events. Uncheck the desired event and save the on-call report again!

Enabling Hidden Events

For preexisting Opsweekly installations, one simply needs to execute the alter_oncall_weekly.sql script to add support for hidden events.

For new installations, opsweekly.sql has been extended to provide that support.

Disabling Event Versioning

By default, Opsweekly INSERTs a new record for each event every time the user saves the on-call report. This isn't necessary, in general, and will probably break hidden event support. Available in this release is the ability to disable event versioning by defining event_versioning = 'off' in phplib/config.php. When event versioning is disabled, Opsweekly will perform UPDATE operations on existing events instead.

See phplib/config.php.example for a working example.

It is strongly recommended that one disables event versioning. Event versioning is likely to be deprecated in a future release.