Troubleshooting

Time guide Initial checks: approximately 10 to 20 minutes Detailed investigation: approximately 20 to 60 minutes Purpose # Investigate Wazuh agent service state, connectivity, enrollment and telemetry flow.

Time guide Initial checks: approximately 10 to 20 minutes Detailed investigation: approximately 20 to 60 minutes Purpose # Review tenant service health, advisories and workload-specific diagnostics. This public reference consolidates professional support experience developed since March 2022 and uses generic placeholders rather than employer or customer information.

Time guide Initial checks: approximately 10 to 20 minutes Detailed investigation: approximately 20 to 60 minutes Purpose # Review uptime, CPU, memory, storage, services, logs and network state on Linux.

Time guide Initial pod triage: approximately 5 to 10 minutes Restart or scheduling investigation: approximately 15 to 30 minutes Dependency or storage investigation: approximately 30 to 60 minutes Purpose # Use this entry to investigate pods in Pending, Failed, Unknown, CrashLoopBackOff, ImagePullBackOff or repeated restart states.

Time guide Initial node triage: approximately 5 to 10 minutes Resource-pressure investigation: approximately 15 to 30 minutes Host-level investigation: approximately 20 to 45 minutes Purpose # Use this entry when a node is NotReady, workloads cannot schedule, resource pressure is suspected, or platform capacity needs review.

Time guide Basic Flux health check: approximately 5 to 10 minutes Failed reconciliation investigation: approximately 10 to 30 minutes Render, dry-run, reconciliation and validation: approximately 15 to 45 minutes The actual duration depends on repository size, deployment dependencies, controller health and the cause of any reconciliation failure.

Time guide Initial Kustomization checks: approximately 5 to 10 minutes Build or dependency investigation: approximately 15 to 30 minutes Render, dry-run and reconciliation validation: approximately 20 to 45 minutes Purpose # Use this entry when a Flux Kustomization is not ready, reports a build failure, waits on a dependency, or applies an unexpected revision.

Time guide Basic controller health check: approximately 5 to 10 minutes Source or reconciliation investigation: approximately 15 to 30 minutes Purpose # Use this entry when Flux resources are not reconciling, a source is stale, or one of the controllers appears unhealthy.

Time guide Initial checks: approximately 10 to 20 minutes Detailed investigation: approximately 20 to 60 minutes Purpose # Read-only checks for mailbox type, aliases, forwarding, permissions and delivery settings. This public reference consolidates professional support experience developed since March 2022 and uses generic placeholders rather than employer or customer information.

Time guide Initial checks: approximately 10 to 20 minutes Detailed investigation: approximately 20 to 60 minutes Purpose # Workflow for identifying why BitLocker protection is off or suspended and whether maintenance caused it. This public reference consolidates professional support experience developed since March 2022 and uses generic placeholders rather than employer or customer information.