Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated for upcoming 2.0.3

This is a brief overview of the major changes between opEvents releases.

opEvents 2.0.3

This maintenance release is scheduled for 8 Dec 2015.

  • A new page for showing both Current and Recent Events was introduced.
    "Current" events are defined as unacknowledged events within a configurable priority range; this is set with opevents_gui_current_events_priorities (default is 3-10).
    This Current Events page refreshes automatically. Current events are shown with their escalation status (and sorted by priority), whereas recent events are listed in the order of their creation.
  • The default number of events to show in various tables is now configurable:
    1. opevents_gui_dashboard_pagination controls the two dashboard pages
    2. opevents_gui_events_pagination is for the Event List page,
    3. and opevents_gui_console_pagination has two values that control the Current and Recent Event panels, respectively.
  • The End Time selector was moved from the menu bar into the Advanced Search Menu.
  • The Event List page now automatically refreshes.
  • Selecting a different time period no longer disables auto-refreshing, and the default period for the GUI can now be configured with the config setting opevents_gui_default_period.
    The event context period can be configured independently with opevents_gui_event_context_period.
  • The Event Context page now shows the escalation status for the event in question.
  • The dashboard pages now show the events sorted by time, newest first.
  • The logic for automatically acknowledging events was improved.
    A stateful up event now auto-acknowledges the corresponding down event and itself; in the past only the down event was acknowledged. This feature can be disabled by changing the config setting opevents_auto_acknowledge.
  • A new action called acknowledge() is available for your Event Action Policy.
  • Some code inefficiencies were removed, the event colors for priorities 9 and 10 were reworked for better contrast.
  • This version of opEvents will work with MongoDB 2.4 but with reduced robustness,
    and only if you set the new configuration variable db_use_v26_features to 0.
    The installer now checks your local MongoDB's version and warns about this issue.

opEvents 2.0.2

This maintenance version of opEvents was released on 30 Nov 2015.

...