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

Account Pool Monitoring #109

Closed
eschwartz opened this issue Nov 8, 2019 · 2 comments
Closed

Account Pool Monitoring #109

eschwartz opened this issue Nov 8, 2019 · 2 comments

Comments

@eschwartz
Copy link
Contributor

I would like to have better visibility into the state of my DCE Account pool.
Specifically, I would like to how many accounts are in each AccountStatus, and be notified if too many are NotReady, or not enough are Ready.

This would allow us to:

  • dive into reset CodeBuild failures, if too many accounts are failing to reset
  • add more accounts to the pool, if demand for leases grows over time.

As a business analyst type user, I may also be interested to see time-series graphs of lease usage (how many account are Status=Leased)


I'm thinking we can put together a simple Lambda that runs every hour, and queries DynDB on the AccountStatus GSI. Then write the results to three different custom CW event metrics (one for each status).
We can configure alarms against these events, and maybe create a CW Dashboard for quick viewing.

@kapilt
Copy link
Contributor

kapilt commented Nov 23, 2019

re monitoring, I would suggest monitoring any cloud build status. accurate state metrics are useful as a higher up business level metric, but a cloud build failure at a lower level would represent an actionable failure.

@marinatedpork
Copy link
Contributor

This is added in #271

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

No branches or pull requests

3 participants