Enevo Sensors
Single-pane view of Enevo IoT sensor data and ETL health. Covers service events, container registry status, content type reference data, and live flow run management for the Enevo normalized pipeline.
Page Overview
Enevo Sensors
Browse service events, inspect container and sensor health, review content types, and manage Enevo flow runs
How to Use
Features
Service Events
Stacked bar chart of daily event counts by customer with an alphabetical customer filter dropdown
Container Registry
Per-customer slot and sensor summary with amber highlighting on stale ETL
Content Types
Waste material reference table with staleness indicator when records are overdue for refresh
Flow Trigger
Recent run history for the Enevo normalized pipeline with a manual trigger button
Tab 1: Service Events
The Service Events tab displays up to 500 rows of Enevo service events, aggregated into a stacked bar chart showing daily event counts broken down by customer.
Chart
- X-axis: Date
- Y-axis: Event count
- Series: One color per active customer
- Max rows: 500 (most recent events)
Customer Filter
The customer dropdown is sorted alphabetically. Select one or more customers to isolate their event series in the chart. Display names strip the "Wasteology - " prefix for readability (e.g., "Wasteology - Springfield" displays as "Springfield").
Active Customers
There are 6 active customers with Enevo sensor data. Wasteology HQ is excluded — no sensors are installed at headquarters.
Tab 2: Container Registry
The Container Registry tab shows a per-customer summary of all registered sensor slots and their associated sensors.
Columns
| Column | Description |
|---|---|
| Customer | Display name (Wasteology prefix stripped) |
| Location | Site or address for the container group |
| Slot ID | Enevo slot identifier |
| Sensor ID | Sensor hardware ID assigned to the slot |
| Last Reading | Timestamp of the most recent data point |
| Status | ✓Current or ⚠Stale ETL |
Stale ETL Highlighting
Rows are highlighted amber when the sensor's last_updated timestamp in enevo_normalized is more than the expected ETL cycle duration. This typically indicates the Enevo normalized flow did not process that sensor in the most recent run.
Tab 3: Content Types
The Content Types tab displays the waste material reference table from enevo_normalized.content_types.
| Column | Description |
|---|---|
| Content Type ID | Enevo internal identifier |
| Name | Waste material name (e.g., "Municipal Solid Waste") |
| Category | Broad waste category |
| Last Updated | When this record was last synced from Enevo |
If any last_updated value is more than 1 day ago, the tab header shows an amber badge. Content types rarely change, but a stale indicator suggests the Enevo API sync may be failing for reference data.
Tab 4: Flow Runs
The Flow Runs tab monitors the enevo-service-events-normalized-wasteology Prefect flow.
KPI Row
| KPI | Description |
|---|---|
| State | Most recent run state |
| Last Run | Timestamp of the most recent run |
| Duration | Elapsed time for the most recent run |
Run History
A table of recent runs showing state, start time, and duration. Click any row to open the run detail in Prefect Cloud (opens in a new tab).
Manual Trigger
Click Trigger Run to kick off a new run of the Enevo normalized flow immediately. A confirmation dialog appears before the trigger is sent.
Manual triggers count against your Prefect Cloud concurrency limits. Do not trigger if a run is already in progress — check the KPI row first.
Data Sources
| Schema | Database | Contents |
|---|---|---|
enevo_normalized | PostgreSQL Production | Normalized service events, container registry, content types |
enevo_json | PostgreSQL Production | Raw Enevo API JSON responses (source for the normalized layer) |