CONCEPT LIBRARY / DEVELOPER RESOURCES

Monitoring concepts

Separate inventory, detection, diagnosis and freshness in optical operations.

Concept documentation. Not a production specification. API examples are illustrative, not hosted services.

Monitoring is evidence with context

A useful optical management view answers what is observed, where the observation came from and whether it is current. An attractive topology alone cannot answer those questions. NEXORA's LINKGRID preview demonstrates selection and a sample change using browser state. It does not collect device telemetry, measure optical power or detect faults in a real network.

Inventory and observations are different

Inventory describes intended or recorded objects such as a device, port or fiber route. An observation describes some aspect of an object at a time. A link can remain in inventory while observations are unavailable. A production interface should therefore avoid displaying every known link as healthy merely because no alert has arrived.

Healthy, degraded, unavailable and unknown should have documented meanings. Thresholds must be defined for the actual equipment and measurement. The fictional product family supplies no universal optical alarm threshold. Units and signal direction matter, and combining measurements without checking those details can lead to incorrect conclusions.

Detection is not diagnosis

A warning may indicate a change that deserves investigation, but it rarely establishes a unique cause. An operator may need endpoint observations, physical route records, recent configuration changes and approved inspection procedures. A diagnosis should distinguish evidence from hypothesis. Do not infer a damaged connector solely from a colored link in a visualization.

Inspect the demonstration

Open LINKGRID and run a sample event. Read the selected link context and its explicitly simulated state. In the network lab, inspect both endpoints before tracing a route. The inspector lists adjacency from the current graph. Changing presets resets the selection, avoiding a stale association between an old identifier and a new topology.

Packet events represent a completed visual demonstration. They do not report delivery from remote hardware. Under reduced motion, the highlighted route and text provide the same explanatory result without moving light. No event is sent to a collector or persisted as operational history.

Plan a real monitoring system

A production system would require authorized collectors, secure transport, storage, source timestamps, freshness policies and response procedures. It should make unknown and stale states visible rather than silently filling gaps. Read the API overview for a proposed local schema and infrastructure for physical-to-logical mapping. This educational preview cannot establish an operational baseline, certify availability or replace a real diagnostic workflow.