Skip to content

Task 9: Alertmanager Configuration and Verification #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 49 commits into
base: main
Choose a base branch
from

Conversation

elian-cheng
Copy link
Owner

@elian-cheng elian-cheng commented Dec 14, 2024

Task 9: Alertmanager Configuration and Verification

  1. Task: Alertmanager Configuration and Verification Task Description
  2. PR Link: Alertmanager Configuration and Verification PR
  3. Screenshot:
    Screenshot_32
  4. Completion Date: 14.12.2024
    Deadline: 16.12.2024
  5. Score: 100/100

Evaluation Criteria (100 points for covering all criteria)

  1. Contact Points Created (10 points)

image


  1. Alert Rules Created (40 points)
    • High CPU utilization alert on Kubernetes nodes is configured.
    • Lack of RAM (CPU cores capacity - on the task before edition last week) capacity alert on Kubernetes nodes is configured.
    • Alerts are configured to be delivered to the email address.

Alert Rule Config

Screenshot_35


  1. Alert Rules are Working as Expected (20 points)
    • Alert rules are tested by simulating CPU and memory stress on the node using the stress tool.

Screenshot_31
Screenshot_42
Screenshot_41


  1. Email is Received (10 points)
    • The alert emails are received in the inbox as expected.

Screenshot_43


  1. Additional Tasks (20 points)

    • Documentation (10 points): The Alertmanager setup and alert configuration are documented in the README file.
    • Configuration is Done Completely in Code (10 points): All configuration (Alert Rules, Contact Points, and SMTP settings) is done via YAML files and code-based methods.

    Links:


References

Repository owner deleted a comment from gitguardian bot Dec 14, 2024
Repository owner deleted a comment from gitguardian bot Dec 14, 2024
Repository owner deleted a comment from gitguardian bot Dec 14, 2024
Repository owner deleted a comment from gitguardian bot Dec 14, 2024
Repository owner deleted a comment from gitguardian bot Dec 14, 2024
@elian-cheng elian-cheng force-pushed the 9_alertmanager_configuration branch from b38fcab to 109c488 Compare December 14, 2024 15:11
Repository owner deleted a comment from gitguardian bot Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant