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

dex(metrics): set buckets around expected latency region #4600

Merged
merged 1 commit into from
Jun 12, 2024

Conversation

erwanor
Copy link
Member

@erwanor erwanor commented Jun 12, 2024

Describe your changes

This re-centers the DEX buckets around the expected latency region

Checklist before requesting a review

  • If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

@erwanor erwanor requested review from hdevalence and cratelyn June 12, 2024 18:37
@erwanor erwanor changed the title metrics: set buckets around expected latency region dex(metrics): set buckets around expected latency region Jun 12, 2024
@erwanor erwanor merged commit 06a08f7 into main Jun 12, 2024
13 checks passed
@erwanor erwanor deleted the erwan/buckets_metrics branch June 12, 2024 21:25
conorsch pushed a commit that referenced this pull request Jun 20, 2024
## Describe your changes
This re-centers the DEX buckets around the expected latency region

## Checklist before requesting a review

- [x] If this code contains consensus-breaking changes, I have added the
"consensus-breaking" label. Otherwise, I declare my belief that there
are not consensus-breaking changes, for the following reason:

(cherry picked from commit 06a08f7)
@conorsch conorsch mentioned this pull request Jun 20, 2024
1 task
conorsch pushed a commit that referenced this pull request Jun 20, 2024
## Describe your changes
This re-centers the DEX buckets around the expected latency region

## Checklist before requesting a review

- [x] If this code contains consensus-breaking changes, I have added the
"consensus-breaking" label. Otherwise, I declare my belief that there
are not consensus-breaking changes, for the following reason:

(cherry picked from commit 06a08f7)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants