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

Jump to bottom

x/build: set up Gerrit latency monitoring #32307

Open
bradfitz opened this issue May 29, 2019 · 0 comments
Open

x/build: set up Gerrit latency monitoring #32307

bradfitz opened this issue May 29, 2019 · 0 comments
Labels
Builders x/build issues (builders, bots, dashboards) NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Unreleased

Comments

@bradfitz
Copy link
Contributor

I regularly encounter Gerrit latency & server errors lately but my bug reports to the team are rarely found to be detailed enough to be actionable or reproducible, or are viewed as anecdotal.

We should probably start gathering our own data on Gerrit latency & reliability with enough data to file actionable bug reports.

We could also use said data to see if Gerrit is getting better or worse over time, and to inform any migration decisions we make in the future.

Maybe just set up our own Stackdriver probers from a number of regions?

/cc @dmitshur
@gopherbot gopherbot added this to the Unreleased milestone May 29, 2019
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label May 29, 2019
@dmitshur dmitshur added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label May 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
3 participants
@bradfitz @dmitshur @gopherbot