Skip to content

Conversation

bentranter
Copy link
Member

Tried to see how far I could get adding support for uptime checks and alerts in a day, and this is what I could do.

This is still missing:

  • Integration tests,
  • More in-depth tests for the create check operation, since I added a bit of extra functionality over the default API interaction,
  • The get state method for checks. It has a different displayable type, so it was too much work for today,
  • All of the uptime alerts, since it's a separate set of endpoints.

Not sure if we want to merge as-is, but I figured it's probably better than not having the functionality. I'll try to complete it on the next free Friday.

Tried to see how far I could get adding support for uptime checks and
alerts in a day, and this is what I could do.

This is still missing:

  * Integration tests,
  * More in-depth tests for the `create` check operation, since I added
    a bit of extra functionality over the default API interaction,
  * The `get state` method for checks. It has a different displayable
    type, so it was too much work for today,
  * All of the uptime alerts, since it's a separate set of endpoints.

Not sure if we want to merge as-is, but I figured it's probably better
than not having the functionality. I'll try to complete it on the next
free Friday.
@bentranter bentranter requested a review from a team June 30, 2023 19:53
Copy link
Member

@danaelhe danaelhe left a comment

Choose a reason for hiding this comment

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

👍

@bentranter bentranter merged commit 21a1d55 into digitalocean:main Jul 6, 2023
@bentranter bentranter deleted the uptime-checks branch July 6, 2023 16:05

DigitalOcean Uptime Checks provide the ability to monitor your endpoints from around the world,
and alert you when they're slow, unavailable, or SSL certificates are expiring.`,
},
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
},
GroupID: manageResourcesGroup,
},

After #1387 landed, we need to remember to GroupID to get them categorized right. As is, it shows up under Additional Commands.

Also, should this maybe be nested under the existing monitoring command? That would mirror the control panel experience.

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