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

Increase inventory canary scalability #732

Open
Chriscbr opened this issue Jan 27, 2022 · 2 comments
Open

Increase inventory canary scalability #732

Chriscbr opened this issue Jan 27, 2022 · 2 comments
Labels

Comments

@Chriscbr
Copy link
Contributor

If there are too many packages, the canary will time out and metrics will no longer be available for operators.

@Chriscbr Chriscbr added the p2 label Jan 27, 2022
rix0rrr pushed a commit that referenced this issue Jan 28, 2022
On the public Construct Hub we've received alarms about the inventory canary timing out due to the large number of packages it is trying to analyze. This inventory canary isn't critical to the Construct Hub's customer-facing behavior since none of the metrics are directly tied to other alarms, so I've changed the alarm to low severity.

I also increased the timeout / schedule rate of the canary to resolve the actual timeout issue we are having, and created the issue #732 for tracking a long-term fix.
@gabewomble
Copy link
Contributor

@Chriscbr I saw a related pull request was merged for this issue, can this now be closed?

@Chriscbr
Copy link
Contributor Author

@gabewomble For this issue I was more thinking about when our package library gets larger and increasing the timeout is no longer an option since there's a 15 minute limit on Lambda functions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants