Bird
0
0

You want to silence alerts for a maintenance window using Alertmanager. Which configuration snippet correctly silences alerts with label 'job=database' for 2 hours?

hard📝 Workflow Q8 of 15
Kubernetes - Monitoring and Logging
You want to silence alerts for a maintenance window using Alertmanager. Which configuration snippet correctly silences alerts with label 'job=database' for 2 hours?
Asilences: - matchers: - name: 'job' value: 'database' isRegex: false startsAt: '2024-01-01T10:00:00Z' endsAt: '2024-01-01T12:00:00Z'
Bsilences: - match: job: 'database' duration: 2h
Csilences: - matcher: - job: 'database' start: now end: 2h later
Dsilences: - matchers: - name: 'job' value: 'database' isRegex: true startsAt: '2024-01-01T10:00:00Z' endsAt: '2024-01-01T12:00:00Z'
Step-by-Step Solution
Solution:
  1. Step 1: Understand Alertmanager silence format

    Silences use 'matchers' with 'name', 'value', and 'isRegex' fields, plus 'startsAt' and 'endsAt' timestamps.
  2. Step 2: Identify correct syntax for 2-hour silence

    silences: - matchers: - name: 'job' value: 'database' isRegex: false startsAt: '2024-01-01T10:00:00Z' endsAt: '2024-01-01T12:00:00Z' correctly uses matchers and ISO8601 timestamps for start and end.
  3. Final Answer:

    Correct silence config with matchers and timestamps -> Option A
  4. Quick Check:

    Silence uses matchers + start/end times [OK]
Quick Trick: Silences need matchers and exact start/end times [OK]
Common Mistakes:
  • Using 'match' instead of 'matchers'
  • Using duration instead of timestamps
  • Setting isRegex true when not needed

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes