Skip to content

feat(metrics): add metric for builder proxy being up #143

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

Closed
wants to merge 1 commit into from

Conversation

paranoiacblack
Copy link

Adds a metric, "rpc.builder_up" that indicates whether the builder proxy is responding to requests. If the builder proxy returns 500 Internal Server Error, the builder proxy is reported as down. Otherwise, the builder proxy is reported as up.

This is a valuable feature for chain operators running rollup boost who need to track the status of the remote builder.

Adds a metric, "rpc.builder_up" that indicates whether the builder proxy is responding to requests.
If the builder proxy returns 500 Internal Server Error, the builder proxy is reported as down.
Otherwise, the builder proxy is reported as up.

This is a valuable feature for chain operators running rollup boost who need to track the status of the remote builder.
Copy link

vercel bot commented Mar 21, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
rollup-boost ⬜️ Ignored (Inspect) Visit Preview Mar 21, 2025 3:46am

@0xForerunner
Copy link
Collaborator

0xForerunner commented Mar 21, 2025

I'm not sure this is any more useful than just keeping a histogram for builder responses with a status label attached. I would personally prefer that approach. There's already an open PR which includes this functionality as well. I believe this is in #135.

@0xKitsune
Copy link
Collaborator

Closing for now as metrics to track builder responses were included in #135. Feel free to open an issue if there are additional metrics that should be added.

@0xKitsune 0xKitsune closed this May 8, 2025
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