AuditorUnavailable

Runbook: AuditorUnavailable

Alert Details

• Alert Name: AuditorUnavailable
• Expression: max (pull_audit_new_jobs_queue) without (cluster, prometheus, prometheusK8sClusterProvider) > 0

Description

This alert triggers when the maximum value of the audit jobs queue exceeds a certain threshold, indicating that the auditor service is unavailable or not processing jobs.

Possible Causes

• The auditor service is down or not running.
• High volume of audit jobs causing delays.
• Network issues affecting the auditor service.
• Configuration errors in the auditor setup.

Troubleshooting Steps

1. Check Auditor Service Status

   • Command: systemctl status auditor-service
   • Expected Output: The status of the auditor service. Look for “active (running)”.
   • Example:

     1 2 3 4

     $ systemctl status auditor-service ● auditor-service.service - Auditor Service Loaded: loaded (/etc/systemd/system/auditor-service.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2024-11-13 14:00:00 UTC; 19min ago

2. Restart Auditor Service

   • Command: sudo systemctl restart auditor-service
   • Expected Output: The service restarts without errors.
   • Example:

     1	$ sudo systemctl restart auditor-service

3. Check Network Connectivity

   • Command: ping -c 4 auditor-service-hostname
   • Expected Output: Successful ping responses.
   • Example:

     1 2 3 4 5 6

     $ ping -c 4 auditor-service-hostname PING auditor-service-hostname (192.168.1.3) 56(84) bytes of data. 64 bytes from auditor-service-hostname: icmp_seq=1 ttl=64 time=0.123 ms 64 bytes from auditor-service-hostname: icmp_seq=2 ttl=64 time=0.124 ms 64 bytes from auditor-service-hostname: icmp_seq=3 ttl=64 time=0.125 ms 64 bytes from auditor-service-hostname: icmp_seq=4 ttl=64 time=0.126 ms

4. Verify Auditor Configuration

   • Command: cat /etc/auditor-service/config.yml
   • Expected Output: Configuration file contents. Ensure all settings are correct.
   • Example:

     1 2 3

     $ cat /etc/auditor-service/config.yml job_name: 'audit-jobs' max_queue_age: 300

Additional Steps

• Check Logs for Errors

  • Command: journalctl -u auditor-service --since "1 hour ago"
  • Expected Output: Recent logs for the auditor service. Look for any error messages.
  • Example:

    1 2 3 4

    $ journalctl -u auditor-service --since "1 hour ago" -- Logs begin at Wed 2024-11-13 13:00:00 UTC, end at Wed 2024-11-13 14:00:00 UTC. -- Nov 13 13:45:00 hostname auditor-service[1234]: Auditor job processed Nov 13 13:50:00 hostname auditor-service[1234]: Error: Job processing delayed

• Check Underlying Infrastructure

  • Ensure the server hosting the auditor service is up and running.
  • Verify there are no ongoing maintenance activities or outages.