Events

Events

Review downtime events, narrow the list on the server, page through it and export recorded results.

Events is an early-access feature. It appears when your plan includes it and you have permission to read events.

Open Insight → Monitor → Events to review downtime across your sites. Each row shows Asset / Site, Started / Ended, State / Origin, Category / Responsibility and Lost output / Quality. The asset name links to the event record, where you can read and change one event.

The Events list with its filters, the matching and unclassified counts, and Classify selected

Open means no end has been recorded. Closed means an end is recorded. Unwatched means the event remains open but its alarm no longer watches it; the row shows the recorded reason, or says the reason is unavailable. The list does not turn a missing end into a closed event. Below the state, the row shows the origin as recorded, for example manual for an event a person recorded or alert for one an alarm opened.

Names come from reads you are allowed to make. A missing or inaccessible name has an explicit unavailable label. A name being unavailable does not erase the recorded event.

Who can do what

RoleEvents
ViewerRead the list, the event records and the export
Operator, AdminAlso select and classify events, and change an event on its record

Classification and the Categories and Responsibility filters also need an installed classification vocabulary you can read. Without it the page says Classification vocabulary unavailable.

If your plan does not include Events, the page says Events is not included in your plan. If access could not be checked, it says so and offers Retry access check. Neither message means your events are gone.

Narrow the list

On smaller screens, choose Filters to open the controls. Use Sites, Assets, Categories, Responsibility, States and Classification. Choose a site before choosing an asset. Previous assets and More assets browse the site's asset choices.

Set From (UTC) and To (UTC) to find events that overlap a time range. The range controls use UTC; event times in the rows use your browser's local time after the page loads.

The filters run on the server across every event you can read, not only the rows on screen. They stay in the page URL, so a link opens the same view. Changing a filter starts at the first page and clears your selection. Clear filters widens the view and clears the selection.

The matching count describes the current filters. The unclassified count uses those same filters except Classification, so you can see how much of that population has no confirmed classification. An agent proposal does not make an event classified. Unavailable means the count was not provided or could not be read; it does not mean zero.

Page through events

The list shows 50 events a page, newest start first, then event ID, so the order is the same on every visit. The line below the table says which rows you see, for example 1–12 of 12. Previous and Next move one page and keep your filters. A page change clears your selection, because a selection belongs to the page it was made on.

If the list cannot be read, the page shows the reason and Retry events.

Export CSV

Choose Export CSV to download all events matching the current filters, across pages, as events.csv. The export accepts up to 5,000 events. If it exceeds that limit, narrow the filters and try again.

The CSV keeps recorded event IDs, UTC times, the origin and state, any opening alarm, confirmed category and responsibility labels with who confirmed them and when, lost-output values and units, quality, method and unavailable-data reasons where recorded. It does not add the current asset or site names displayed in the list. Empty values are not zero. If export fails, the page shows the reason and you can try again.

Use this export to keep or analyse the event record itself. To check how events count against a service contract, use the contract's availability export instead.

On this page