Eternet Portal Documentation

Operations Dashboard

What it provides

The landing dashboard brings together activity charts, resource counts, recent connections, user activity, and recent locations using the portal’s verified dashboard API contracts.

Data behavior

The page requests five dashboard data groups independently. If one upstream request fails, other available groups can still render and the response is marked partial; the page is not an atomic snapshot.

Values are fetched from the configured Eternet Core API. The interface should be described as API-backed operational visibility, not as a guaranteed push-based live feed.

Operational value

  • Review device, hub, and vehicle totals.
  • Inspect recent activity and connection signals.
  • Use location and chart summaries as a starting point for deeper investigation.

Reading the operational overview

The landing Dashboard is designed to answer a broad set of first questions: how many devices, hubs, or vehicles are represented; what recent connections or user activity have occurred; where recent locations were reported; and how selected activity has changed over a chart interval. It requests separate chart, count, connection, activity, and location resources using the portal’s dashboard API contract. Those results help an operator decide which domain page to open next. The Overview is therefore a summary and navigation aid, not a substitute for the detailed resource workspace or a query builder.

Each data group is fetched independently. The loader uses settled results so one failed upstream call does not necessarily remove every other panel. If some requests reject, the returned model is marked partial. This is a deliberate resilience behavior, but it also means a visible dashboard can contain a mix of fresh and missing information. A production presentation should call out any partial state and confirm the timestamps or refresh behavior for the data group being discussed. A successful page render should not be interpreted as proof that every endpoint responded.

Freshness and interpretation

The page title describes live values, but the code path observed here requests API data when the dashboard loads; it is not by itself proof of a continuous push stream or fixed refresh interval. A recent connection chart may summarize events over a window, while recent location data represents records returned by an API. Counts can reflect backend aggregation rules and may not be synchronized to the same instant as the other panels. Customers should understand the source and time semantics of each widget before comparing values across panels.

If a count is unexpectedly zero, verify authentication, endpoint success, user scope, and the response shape before concluding that no resources exist. If activity appears stale, inspect the last event time and upstream refresh process. For operational incidents, use the relevant device, vehicle, or hub detail page to inspect identifiers, streams, and raw values.

Customer value

The Overview provides an at-a-glance orientation across the Eternet environment. It can shorten the path from a broad signal to the resource that needs investigation and give managers a shared starting view. Its value is strongest when data contracts, timestamps, and permissions are consistent. Before presenting, confirm that each dashboard endpoint returns the intended tenant’s data, identify which panels are partial, and verify that map coordinates and counts match a known sample. The portal aggregates and presents backend summaries; the underlying services remain responsible for the source records and calculations.