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

Regular outages not reported by status page #482

Closed
jkfm opened this issue Nov 28, 2024 · 1 comment
Closed

Regular outages not reported by status page #482

jkfm opened this issue Nov 28, 2024 · 1 comment
Assignees
Labels
customer/feedback Feedback from customers kind/bug Some behavior is incorrect or out of spec
Milestone

Comments

@jkfm
Copy link

jkfm commented Nov 28, 2024

Hi,

we regularly have the problem that in the afternoon (CET) it's not possible to open an environment to show secrets and variables. Neither the web interface nor CLI works. All requests fail with 504 errors with a hint that there may be too much traffic.

At the same time, your status page reports that all systems are operational. To me, that is really misleading since it's clearly not a one-off but sustained problem.

When can I expect that this will be fixed?

Kind regards

@jkfm jkfm added customer/feedback Feedback from customers needs-triage Needs attention from the triage team labels Nov 28, 2024
@cleverguy25 cleverguy25 removed the needs-triage Needs attention from the triage team label Dec 1, 2024
@cleverguy25 cleverguy25 added this to the 0.114 milestone Dec 1, 2024
@mikhailshilkov mikhailshilkov added the kind/bug Some behavior is incorrect or out of spec label Dec 2, 2024
@dschaller
Copy link
Member

Hey @jkfm,

apologies about the delay here - we have been investigating the issue you've been running into and looking into the best approach to solve it.

I've done a write up in pulumi/esc#425 which outlines why we are seeing slow opens for environments using the 1password-provider.

The reason our status page does not reflect any issues when you're unable to open environments is that this is a slightly isolated issue to only environments with either a large number of imported environments using the 1password-provider and/or environments using a lot of 1password secrets. We are actively working with the 1password team to move to a bulk API that should get rid of these latency issues and make opens work consistently for you.

I'm going to close this issue out in favor of the one mentioned above in ESC. Please follow along there for updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer/feedback Feedback from customers kind/bug Some behavior is incorrect or out of spec
Projects
None yet
Development

No branches or pull requests

4 participants