Browsing events and time series

Your assets produce two kinds of data:

• Timeseries are the steady signal — pressure, temperature, flow, measured over time.
• Events are the moments that matter — an alarm fires, a threshold is crossed, a maintenance job runs.

You need both. A pressure chart tells you the reading was climbing. The event tells you someone was working on the valve that morning.

Browsing timeseries

1. Open Timeseries in the top menu. You land on the Explore tab.
2. Use the search field to find a series by name.
3. Click a series to chart it.

Once a series is selected, the time controls appear at the top right. Set a start and end time, or pick a quick range such as Last hour, Last day or Last week.

Every timeseries is connected to the resource it measures. So a chart is never just a line — you can follow it back to the valve, pump or tank it came from.

Creating a timeseries

If the measurement you need does not exist yet:

1. On the Timeseries tab, click the create button.
2. Choose Create Time Series from the menu.
3. Fill in the form:
   • Name — Pressure. The external ID fills in automatically.
   • Unit — click + and pick one, for example bar or °C. The unit is what makes the numbers comparable.
   • Value type — how readings are stored. Measurements with decimals need Float.
   • Resource — click + to link the series to the resource it measures.
   • Dataset — which dataset the measurement belongs to.
4. Click Save.

The series is empty until data flows in. Once readings arrive, it charts on the Explore tab.

Browsing events

Open Events in the top menu. Everything that has happened across your assets lands here, newest activity included, in one list.

The list shows the external ID, type, sub type, status and event time of each event.

Filtering the event log

The filter panel on the left narrows the list down:

• External ID — match events by their identifier.
• Dataset ID — only events from one dataset.
• Start time / End time — the window you care about, in UTC.
• Source — the system that logged the event.
• Type and Sub type — for example an alarm versus a maintenance job.
• Status — where the event stands.
• Metadata — match on the key/value context attached to the event.

Start wide and narrow down. Filtering by time and type usually gets you close in two steps.

Reading a single event

Click any row to open its details:

• Type, sub type and status
• Event time — when it happened
• Description — what happened, in words
• Dataset and source — where it came from
• Metadata — any extra context the source attached
• Related resources — the assets the event concerns

Related resources is the useful part. An alarm is not a line in a log — it points straight at the affected asset, and from there you can open the asset's network and see what else it touches.

Putting the two together

The normal working pattern:

1. Something looks wrong on a chart in Timeseries.
2. Open Events, filter to the same time window and the same asset.
3. Read what happened.

Measurements tell you what changed. Events tell you why.

What to do next

• Chart several series together and stream live data — see the guide on Timeseries Insights.
• Build out the network behind your measurements — see the guide on building a resource network.