Eternet Portal Documentation

Custom Dashboards

Dashboard model

Dashboard records use the established Angular-compatible dashboard model, including a dashboard value with title, path, sections, and cards. The portal can display dashboard definitions and open an individual dashboard route.

Current implementation boundary

The current dashboard listing/creation manager explicitly calls its Mock API route for list, create, and delete. This is a local mock workflow and must not be presented as persisted production dashboard management. A separate settings dashboard page uses Core API contracts for dashboard CRUD and access grants.

Widgets and data

Dashboard card schemas define widget presentation. Live values depend on each resource’s stream data and supported refresh/subscription path; a saved dashboard layout alone does not guarantee that every widget has live telemetry.

What a dashboard definition represents

A dashboard is a structured presentation definition rather than a datasource by itself. In the portal model, a dashboard value can hold a title, short path, sections, and cards. Each card may contain a schema describing how a widget is rendered and may identify a source entity. Sections help organize related signals into an operational view—for example, grouping identity and status separately from trends or location. This structure follows the established Angular-compatible model so definitions can be interpreted consistently across parts of the product. The data shown by a card still comes from its connected resource or stream; a layout can exist even when a value is missing.

When presenting dashboards to customers, explain how the definition is composed: a human-readable title, a route path, sections for information architecture, and cards for individual visual elements. Then clarify which source provides each value and how current it is. A gauge without an update timestamp may show a configured or cached value. A map card needs location fields, and a chart needs a series of values with usable timestamps. The dashboard layer organizes and visualizes these results; it does not automatically create telemetry, repair missing data, or enforce a real-time service-level objective.

Current persistence and administration boundaries

The current Dashboards route uses a manager component that explicitly calls local Mock API routes for listing, creating, and deleting dashboards. This is important for customer communication: the visible workflow demonstrates the dashboard model and presentation, but that specific manager is not evidence of production persistence in the Core API. The Settings → Dashboards route is separate and uses the Eternet dashboard API contracts for administration, including edit/create/delete and access selections. Even there, backend persistence and access enforcement are determined by the service contract and must be validated in the target environment.

Default dashboards are treated specially by the administration UI and are protected from deletion. When a saved record contains only a generic title, the UI can derive a display title from its path or scope to make it easier to distinguish. These presentation choices improve usability but do not alter the underlying record. If a customer asks whether a dashboard is shared, confirm the saved access grants and service-side policy rather than inferring sharing from a visible card.

Customer value and a credible demo

Dashboards can provide a concise entry point for teams that need recurring operational visibility without navigating each device individually. They help customers align the most relevant signals with a role or workflow, and they can make complex systems easier to scan. A good demonstration begins with a dashboard whose source data and persistence behavior are known. Show one section, explain the data source of two cards, and verify a timestamp or current reading. For a production use case, validate the dashboard API, authorization, widget schemas, and live or historical data path end to end. Be transparent that the custom manager’s current Mock API path is for demo/testing and that live dashboards rely on separately configured services.