---
title: "KnovvuCoreFatalLogRules"
slug: "runbooks-knovvu-core-core-fatal-log-rules"
updated: 2025-05-19T13:18:24Z
published: 2025-05-19T13:18:24Z
---

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

# KnovvuCoreFatalLogRules

## Meaning

This alert is triggered when a core service logs more than one fatal-level message within a 1-minute window. Fatal logs indicate unrecoverable errors that typically cause service crashes or major disruptions. The alert fires at a critical level.

**Full context**

Fatal log entries usually reflect catastrophic failures such as unhandled exceptions, corrupted state, or forced shutdowns.

## Impact

- Service likely crashed or entered a failed state.
- Immediate disruption of functionality or data processing.
- Potential cascading impact on dependent systems.

## Diagnosis

- Identify the affected service from the alert label.
- Check logs for fatal errors and stack traces.
- Correlate with system events like deployments, resource spikes, or dependency failures.

## Mitigation

- Restart the service immediately if it has stopped.
- Revert recent changes if fatal errors were introduced during deployment.
- Escalate to engineering for root cause analysis and remediation.