---
title: "Health Impact Categories"
slug: "health-impact-categories"
updated: 2026-02-24T11:48:00Z
published: 2026-02-24T11:48:00Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.lakesidesoftware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Health Impact Categories

Health can be impacted by a variety of metrics. They are primarily taken from performance counters or events.

Health is impacted by Windows events if the following are both true:

- An alarm was triggered by the event
- The level of the event is Error, Warning, or Critical

The health score is written to the database in:

- Ten one-minute intervals, which reset after each 10-minute write to the database.
- Each one-minute interval includes metrics that affect the health of a system.

When we check non-event based health values, we check the output of the performance counters. Those checks run every 15 seconds. The value we get is the average of the last 15 seconds.

> [!NOTE]
> **EXAMPLE**: To affect the health score, the average CPU usage for a 15-second interval must be greater than 20%. If the CPU usage spikes to 90% for 1 second, but stays low at 1% for 14 seconds, then the average CPU usage would only be 7%. In this example, there is no health impact.