Events View

Being developed for 3.3.1.

Uses runtime's event data.

Base URL: /event. This loads the javascript application. Everything else loads dynamically after that.

Updates: /event?output=json. This returns JSON data for the table to render

• Server side ordering and filtering of event data
• Data shows host and service data
• Use runtime database
• Clicks on names stays in the “events app”. Popups provide links to status or configuration
• Filtering handled through URL parameters
• Primarily use JSON for page to webservice (not mini html)
• JSON should return non-localised information. Exception is time, which should have timezone information applied
• Lists only returns columns requested (always event id)

Opsview Base:

• jquery.dataTables.js for jQuery based table kit: http://www.datatables.net/
• tango-icons for icons: http://tango.freedesktop.org/Tango_Icon_Library
• Prototype extensions for browser history [link]
• timeline for the time line library: http://www.simile-widgets.org/timeline/

Opsview Core:

• events.js - Opsview specific code for this page
• ajaxdatatable.js - Opsview abstraction layer for using datatables.js

# On a running system
$ opsview-core/utils/dump_events -u root | gzip -c > /tmp/events.gz
# Transfer to development system
$ gunzip -c /tmp/events.gz | mysql -u root