mod: update github.com/elastic/mito to v1.23.1#48500
Merged
Merged
Conversation
efd6
added
Filebeat
botelastic
Bot
added
needs_team
6 tasks
Contributor
🤖 GitHub commentsJust comment with:
|
This picks up elastic/mito@d017a1f which fixes rate period scaling. ref: elastic/mito#119
Contributor
Author
|
/test |
1 similar comment
Contributor
Author
|
/test |
Contributor
Author
|
Test failures are unrelated. |
Contributor
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
andrewkroh
approved these changes
Jan 22, 2026
This was referenced Jan 23, 2026
Member
|
It looks like the failing tests that are blocking this fix from merging are being worked on:
|
Member
|
Force merging past known flaky tests. |
5 tasks
brijesh-elastic
added a commit
to elastic/integrations
that referenced
this pull request
Feb 27, 2026
The httpjson input's limitPolicy function in mito incorrectly scaled the rate period by the window duration, producing a rate in s^-2 instead of s^-1. This made rate limiting far more restrictive than the server's headers indicated for any window > 1s. The fix landed in mito v1.22.1, v1.23.1, and v1.24.1, which were picked up in beats v8.19.11 (elastic/beats#48500) and v9.2.5 (elastic/beats#48526). Bump the Kibana version constraint to match. ref: elastic/mito#119
ilyannn
pushed a commit
to elastic/integrations
that referenced
this pull request
Feb 28, 2026
The httpjson input's limitPolicy function in mito incorrectly scaled the rate period by the window duration, producing a rate in s^-2 instead of s^-1. This made rate limiting far more restrictive than the server's headers indicated for any window > 1s. The fix landed in mito v1.22.1, v1.23.1, and v1.24.1, which were picked up in beats v8.19.11 (elastic/beats#48500) and v9.2.5 (elastic/beats#48526). Bump the Kibana version constraint to match. ref: elastic/mito#119
navnit-elastic
pushed a commit
to navnit-elastic/integrations
that referenced
this pull request
Mar 2, 2026
…tic#17564) The httpjson input's limitPolicy function in mito incorrectly scaled the rate period by the window duration, producing a rate in s^-2 instead of s^-1. This made rate limiting far more restrictive than the server's headers indicated for any window > 1s. The fix landed in mito v1.22.1, v1.23.1, and v1.24.1, which were picked up in beats v8.19.11 (elastic/beats#48500) and v9.2.5 (elastic/beats#48526). Bump the Kibana version constraint to match. ref: elastic/mito#119
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Note
This is a manual backport to 8.19 of #48499.
Checklist
stresstest.shscript to run them under stress conditions and race detector to verify their stability../changelog/fragmentsusing the changelog tool.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs