-
Notifications
You must be signed in to change notification settings - Fork 39
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
add digitalocean_incidents #9
Conversation
Nice! That's definitely super handy! |
@metalmatze Sadly, no. That would have made things much simpler! Their status page service seemed to be the only place, but it has a really great API. |
Ok. Not a blocker at all. Just wanted to check. I'll give it a proper review soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Finally gotten around to do a proper review!
This is definitely an amazing addition to the project.
I added some comments on the code. Let me know what you think!
As a follow up, I think it would be amazing to even add labels for the regions and components, so that I can alert on DNS in FRA1 being down, cause I ultimately might not care about SFO1
@metalmatze Addressed both of the issues and added the ability to filter by region. You can test the regional functionality by changing the API URL to the incident history endpoint(if there aren't any active incidents):
|
@metalmatze just a gentle reminder 😇 |
@circa10a Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for this. 👍
Sorry for the long wait, this isn't the top of my priority list most of the time.
Add a gauge to monitor the number of active incidents with digitalocean services.
Sourced from their status api