Skip to content
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

feat(alerting): magic alerting severities #127

Merged
merged 13 commits into from
Dec 27, 2024
Merged

Conversation

fourstepper
Copy link
Contributor

No description provided.

@fourstepper fourstepper force-pushed the feature/auto-alert-rule branch from 6f30998 to 484b459 Compare September 24, 2024 08:17
Copy link
Contributor

@Hy3n4 Hy3n4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

internal/config/utils.go Outdated Show resolved Hide resolved
@fourstepper fourstepper force-pushed the feature/auto-alert-rule branch from 739c82c to f6de5e2 Compare October 1, 2024 09:33
@fourstepper
Copy link
Contributor Author

Closes #103

@fourstepper fourstepper added this to the Usable milestone Oct 1, 2024
Hy3n4 and others added 3 commits November 30, 2024 22:29
when deploying dev infratructure

Signed-off-by: Hy3n4 <[email protected]>
* feat(alerting): alertmanager config loader

Signed-off-by: Robin Opletal <[email protected]>

* generated stuff...

Signed-off-by: Robin Opletal <[email protected]>

---------

Signed-off-by: Robin Opletal <[email protected]>
@Hy3n4 Hy3n4 force-pushed the feature/auto-alert-rule branch 3 times, most recently from 809ab8d to 38e56e7 Compare November 30, 2024 22:26
mainly fixed duration issues
also, added some feature to devel, osko dashboards, kustomize for asier
deployment and other cool stuff
modified function responsible for creating the alerting rule when
magiAlerting is enabled, also added some basic mapping for opsgenie,
pagerduty and custom alerting tool. Currently not working as expected
tho

Signed-off-by: Hy3n4 <[email protected]>
@Hy3n4 Hy3n4 force-pushed the feature/auto-alert-rule branch from 38e56e7 to 6b30062 Compare November 30, 2024 22:26
Comment on lines +297 to +300
if baseWindow == "5m" || baseWindow == "30m" || baseWindow == "1h" || baseWindow == "6h" ||
baseWindow == "24h" || baseWindow == "3d" || baseWindow == "2h" {
alertRuleErrorBudgets = append(alertRuleErrorBudgets, rules["burnRate"][baseWindow])
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what are we trying to do with the if?

@fourstepper fourstepper force-pushed the feature/auto-alert-rule branch from b26a8d6 to 795e620 Compare December 27, 2024 21:55
@fourstepper fourstepper merged commit 5ff41f5 into main Dec 27, 2024
2 checks passed
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.

3 participants