Observations and troubleshooting
Applies to: Arcturus public demonstrations
Updated
Arcturus separates the condition being observed from the work recorded in response. Read those two parts together: a maintenance action can be recorded after a measurement, while the measurement retains its original time and meaning.
Interpreting the view#
| Item | What it tells you | What to check next |
|---|---|---|
| Observation timestamp | When the source reported the value. | Whether the sample is recent enough for the decision. |
| Unit and threshold | How the reading is expressed and why it may require attention. | Whether the threshold applies to this asset and operating condition. |
| Unavailable value | The source did not provide a usable observation. | Connection, source capability and the reason shown. Do not read it as zero. |
| Last observed data | A retained sample is available, but may be stale. | Original timestamp and the reason a fresh sample is absent. |
| Acknowledged signal | An operator has recorded awareness. | Investigation and corrective work still required. |
| Completed maintenance or resolved incident | The workflow record changed state. | Independent observation that the condition has recovered. |
Missing sensors and counters#
Different sources expose different observations. An absent temperature, power or device-health value cannot be reconstructed from CPU utilization or installed capacity. Read the source explanation and report the missing capability when defining a connected evaluation.
In the public demonstration, measurements are fixed sample data. A simulated inspection adds a local action record without changing those measurements. The timestamps may therefore remain old while the action history contains a newer time.
Browser state and privacy#
The public demo keeps acknowledgements, maintenance work and simulated incidents in the current browser when storage is available. The data is not a shared team incident register. Moving to another browser, using a temporary browsing session, clearing site data or resetting the demo can remove that state.
When persistent storage is unavailable, the demonstration can retain actions only for the current session. Export needed examples before closing the page. Enter fictional notes; there is no reason to place customer records or credentials in a public product demonstration.
Common problems#
| Symptom | Resolution |
|---|---|
| No signals appear | Return to All signals and check the selected workspace. |
| A host shows no metrics | Read the source status. The unavailable sample intentionally has no current observation. |
| A second incident is not created | Check for an existing open incident on that host and finding. |
| A sample incident cannot be resolved | Use an incident created locally in the demo; bundled examples can be read-only. |
| A reset removes previous notes | Reset clears the demo's saved workflow state. Re-enter only disposable examples. |
| An export has sample host names | Expected: the public interface exports synthetic demonstration data. |
Request support#
Report the preview URL, selected workspace and host, visible control, expected result and actual behavior. Include the browser version and whether storage was blocked. For a connected evaluation, also include the product package and observation source; provide sensitive records only through the agreed support channel.