provectus/swiss-army-kube

Improve alerting

Open

#143 opened on Jan 21, 2021

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Python (38 forks)auto 404
enhancementgood first issuesak-prometheussak-scaling

Repository metrics

Stars
 (148 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

For the monitoring system, we need to configure a typical set of alerts and several channels (mail, slack, webhook). This set should respond to common problems, such as lack of disk space, CPU or Memory usage, reaching limits on the number of pods per node, or the limit value of ASG groups.

For example: https://awesome-prometheus-alerts.grep.to/rules.html

Contributor guide

Research direction
Study the Prometheus alert rules from the referenced link and adapt them to the existing monitoring setup in the Swiss Army Kube infrastructure. Determine the appropriate channels (mail, Slack, webhook) and configure them in the monitoring system.
Tech stack
prometheuskubernetesaws
Domain
devopsinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesPrometheusAWS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60