Add alerting #59
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
elbforge/elf-infra#59
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
e.g. alertmanager
@m4rc3l wrote in #59 (comment):
This is not a sensible threshold in general. A relative threshold could make sense for small filesystems but it might not be useful for large filesystems. More important than the free space (which I would set to at least 90% for most use cases) is the grow rate.
Please also add the the inode usage!
The status page should contain outages or performance issues… the alerts from above are not (directly) related with such issues 🤔
The alerting system calls a reverse status check at status.elbforge.org so that we enshure the alerting is running. Like it's done with the route servers at dd-ix
maybe also something along the lines of "more than 20 signups in the last minute" (as soon as signups are live)
HAProxy: