Eternet Portal Documentation
Hub Management
Inventory and detail
The Hubs section loads hub resources and their dashboard data, then opens a shared entity workspace for hub-specific information.
Monitoring
Depending on the API response, operators can inspect hub properties, state-oriented data, streams, and configured dashboard widgets. Historical or current values are only available when the corresponding stream and backend data are present.
Integration boundary
Hub identity and metadata come from the Eternet Hub/Core APIs; stream and state information is supplied by the hub and stream services. The portal presents those results and does not itself act as a hub broker.
Hub lifecycle and operator workflow
A hub usually represents a gateway or integration point that makes downstream state visible to the platform. Operators begin with the inventory to locate the correct hub, then open its detail workspace to understand its identity and the information currently exposed by its services. The page brings together the hub record and the dashboard/stream material returned for that hub. This is especially useful when support staff need to answer whether the platform recognizes a gateway, which states or streams are associated with it, and whether its most recent data is available for inspection.
It is important to distinguish hub configuration from observed hub behavior. A registered hub and a selected hub type describe what the platform expects; they do not prove that the gateway is online now. State records are observations supplied by the connected integration, and timestamps determine how current those observations are. A dashboard card is a visualization of a configured property, not a new source of truth. If a customer asks whether a particular signal is supported, confirm the stream identifier, value type, schema, and live or historical data path rather than relying on the widget’s label alone.
Data quality and fault isolation
The hub experience uses API responses for its resource list and dashboard data. If one request is unavailable, the page can show incomplete information; a missing card does not always mean the hub has no capability. A careful diagnosis checks authentication first, then hub inventory access, hub-specific dashboard data, stream metadata, and the originating integration. Compare the hub’s expected identifiers with actual event or state names, and review timestamps before interpreting an empty or unchanged value. Where an upstream hub integration is temporarily offline, the portal may still display the last stored or configured information. It should not label such information as a fresh live reading unless the source provides a current timestamp or connection state.
Historical records, when exposed by the connected services, support trend review and incident investigation. They are separate from live state updates and may have different retention or query limits. A successful page load therefore confirms only that the portal rendered the available response; it does not guarantee that every connected device behind the hub is reachable or that every message has been retained.
Customer value and demonstration guidance
For customers, Hubs provides a practical view between infrastructure and the devices or states it aggregates. It can make gateways easier to identify, reduce the time needed to find associated data, and provide a consistent detail workspace alongside Devices and Vehicles. To demonstrate it responsibly, choose a hub whose API record, state or stream, and dashboard schema are already known. Show the hub identity first, then one configured value with its source and timestamp. If demonstrating live updates, send a controlled message through the real integration and verify that the right hub changes. Make clear that the portal is the monitoring and management surface: connectivity, state generation, and message delivery are handled by the hub and backend systems.