Investigate a data-center condition

This walkthrough uses the public Data center demonstration. Its equipment and observations are representative, and its maintenance records are local to the browser. Open the data-center preview before beginning.

Find the condition#

1. Enter the Data center workspace and open its signals view.
2. Review the signal's affected asset, reading, unit and observation time. Use the filters to narrow the view or return to All signals if nothing matches.
3. Select Investigate signal for the cooling-loop condition.

The investigation shows the observation and its configured threshold. Compare the value with the unit and threshold label before interpreting the severity. The scenario demonstrates a cooling change; it does not assert that every dependent service has failed.

Examine the time window#

Use the 1h, 6h and 24h observation-window controls to examine the representative trend. The selected window changes the displayed scenario history. It does not ask a live facility for new measurements.

Read the Source & threshold information with the chart. A line rising above a threshold is a reason to inspect the underlying condition. Determining the cause may require additional observations or a physical check of the relevant equipment.

Follow the dependency impact#

Review Dependency impact to see which racks and services are associated with the asset. For the cooling example, the relationship connects the cooling loop to affected racks and the services placed there. That relationship describes exposure to the condition; the service's own state remains a separate observation.

Open Asset evidence when you need the equipment context. Compare it with the recommended checks before deciding the next maintenance step.

Record the next action#

Choose Plan maintenance. Record the responsible person, the intended window and a concise note describing the inspection or work to perform. Use fictional information in the public demonstration.

The maintenance queue distinguishes planned, in-progress and completed work. Move the demonstration plan through those states to examine how the next operator would understand it. Marking a plan complete changes the workflow record; it does not alter the sample observation or perform maintenance on equipment.

Acknowledge and revisit#

Acknowledge records that the condition has been seen. It should not be read as proof that the cause was corrected. Reopen the signal and check the observation separately from its acknowledgement and maintenance state.

If the view is empty, clear the current filter. If a local plan disappears after changing browsers or clearing site data, review the browser-state explanation. Export or record anything you need before resetting the demonstration.