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

Recreate sustained alerts for Arch-BOM in Datadog #830

Open
4 tasks
timmc-edx opened this issue Oct 16, 2024 · 1 comment
Open
4 tasks

Recreate sustained alerts for Arch-BOM in Datadog #830

timmc-edx opened this issue Oct 16, 2024 · 1 comment
Assignees

Comments

@timmc-edx
Copy link
Member

timmc-edx commented Oct 16, 2024

We had to disable Arch-BOMs "sustained" alerts after the move from New Relic to Datadog because DD does not have the ability to monitor on an alert condition staying above/below a threshold for an extended interval. Some were recreated but were eventually paused or had their sensitivity turned down to the point of uselessness.

"Sustained" monitors have a counterpart "burst" monitors. Burst monitors are for a large change over a short time interval, while sustained monitors look for a smaller change over a longer time interval. The idea is to detect slower drift that's otherwise swamped by noise.

Now that we have some options laid out in https://2u-internal.atlassian.net/wiki/spaces/ENG/pages/1581023295/Options+for+Datadog+time-period+APM+monitors we can try recreating them. We'll need to try some out and turn that document into a how-to, complete with cautions and advice. It may also need to be linked to from monitors to explain why they're configured in an unusual way. (For example, if we use renotification, monitors may be in an "alert" state even though they aren't firing, and we'll want the doc page to explain this.)

Acceptance Criteria:

@timmc-edx timmc-edx converted this from a draft issue Oct 16, 2024
@timmc-edx
Copy link
Member Author

Blocked on #691

@timmc-edx timmc-edx moved this from Ready For Development to Blocked in Arch-BOM Dec 16, 2024
@robrap robrap removed the status in Arch-BOM Jan 27, 2025
@timmc-edx timmc-edx moved this to Ready For Development in Arch-BOM Jan 28, 2025
@robrap robrap moved this from Ready For Development to Backlog in Arch-BOM Jan 29, 2025
@rayzhou-bit rayzhou-bit self-assigned this Feb 12, 2025
@rayzhou-bit rayzhou-bit moved this from Backlog to In Progress in Arch-BOM Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

2 participants