- 2 minutes to read

Expected State

Use Expected State to override how Nodinite evaluates a monitored Resource. This helps teams reduce alert noise during planned maintenance, known issues, and controlled operational windows while keeping full visibility in Monitor Views.

Key benefits:

  • ✅ Reduce false alerts during planned maintenance and controlled downtime
  • ✅ Keep operators informed with a visual indicator when real and expected states differ
  • ✅ Document intent using the Description field for transparency and audits

How Expected State Works

A Monitoring Agent discovers and reports the current state for each Resource. The Monitoring Service evaluates that state and publishes it to Monitor Views.

When you configure Expected State, Nodinite applies your override rule to the evaluation result. Each state override is explicit and traceable, and the original condition is still visible to users through a colored dot indicator.

Expected state
Example of configuring expected state to handle intentionally disabled or stopped resources. The Description field documents why monitoring evaluation was overridden.

Expected state icon
Example of the colored dot indicator showing the real state when expected state differs from actual state.

Common Scenarios

  • Planned maintenance - A service is intentionally stopped for patching.
  • Known issue window - A temporary condition is accepted while a permanent fix is in progress.
  • Business schedule - A component only runs during office hours and should not raise off-hours alerts.

Use the Description Field

For every override, add a clear Description so other operators understand the reason:

  • Planned maintenance - "App Pool stopped for weekend patching every Saturday 2-6 AM"
  • Known issues - "Warning expected until database upgrade completes"
  • Business requirements - "Service runs Mon-Fri 8 AM - 6 PM"
  • Temporary overrides - "Suppress during migration, remove after go-live"

Descriptions improve handovers, troubleshooting quality, and audit readiness.

State / Status Code Values

Internally, Nodinite uses the following status code values:

State Status Code value
OK 0
Warning 1
Error 2
Unavailable 3
Connection Error 4

Expected State and Auto Healing

Expected State controls how state is interpreted. Auto Healing controls what action is executed when an evaluated state is detected.

Use both together for robust operations:

  • Apply Expected State when a condition is intentional.
  • Configure Auto Healing when a condition should trigger remediation through Remote Actions.

Next Step

Add or manage Resource
Auto Healing
Monitor Views

Resources
Monitoring Agents
Monitoring Service
Remote Actions