Skip to content

[9.2](backport #48499) mod: update github.com/elastic/mito to v1.22.1#48526

Merged
efd6 merged 2 commits into
9.2from
mergify/bp/9.2/pr-48499
Jan 24, 2026
Merged

[9.2](backport #48499) mod: update github.com/elastic/mito to v1.22.1#48526
efd6 merged 2 commits into
9.2from
mergify/bp/9.2/pr-48499

Conversation

@mergify

@mergify mergify Bot commented Jan 23, 2026 •
edited by efd6
Loading

Copy link
Copy Markdown
Contributor

Proposed commit message

mod: update github.com/elastic/mito to v1.22.1

This picks up elastic/mito@cf9d7cc which fixes rate period scaling.

ref: elastic/mito#119

Note

The backport to 8.19 will be constructed manually: #48500

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
  • I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

This is an automatic backport of pull request #48499 done by [Mergify](https://mergify.com).

@mergify mergify Bot added backport conflicts There is a conflict in the backported pull request labels Jan 23, 2026
@mergify mergify Bot requested review from a team as code owners January 23, 2026 19:39
@mergify

mergify Bot commented Jan 23, 2026

Copy link
Copy Markdown
Contributor Author

Cherry-pick of c17c95d has failed:

On branch mergify/bp/9.2/pr-48499
Your branch is up to date with 'origin/9.2'.

You are currently cherry-picking commit c17c95d6f.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   changelog/fragments/1769025726-mito1241.yaml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt
	both modified:   docs/reference/filebeat/filebeat-input-cel.md
	both modified:   go.mod
	both modified:   go.sum

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@mergify mergify Bot added the backport label Jan 23, 2026
@mergify mergify Bot assigned efd6 Jan 23, 2026
@mergify mergify Bot added the conflicts There is a conflict in the backported pull request label Jan 23, 2026
@botelastic botelastic Bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 23, 2026
@mergify mergify Bot requested review from leehinman and rdner and removed request for a team January 23, 2026 19:39
@github-actions

github-actions Bot commented Jan 23, 2026

Copy link
Copy Markdown
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@github-actions github-actions Bot added Filebeat Filebeat bugfix Team:Security-Service Integrations Security Service Integrations Team labels Jan 23, 2026
@botelastic botelastic Bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jan 23, 2026
@elasticmachine

elasticmachine commented Jan 23, 2026

Copy link
Copy Markdown
Contributor

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@efd6
mod: update github.com/elastic/mito to v1.24.1 (#48499)
4eed50b 
This picks up elastic/mito@f9b0830 which fixes rate period scaling.

ref: elastic/mito#119
(cherry picked from commit c17c95d)
@efd6 efd6 force-pushed the mergify/bp/9.2/pr-48499 branch from d1c5d83 to 4eed50b Compare January 24, 2026 01:25
@efd6 efd6 changed the title [9.2](backport #48499) mod: update github.com/elastic/mito to v1.24.1 [9.2](backport #48499) mod: update github.com/elastic/mito to v1.22.1 Jan 24, 2026
@github-actions

github-actions Bot commented Jan 24, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

@efd6 efd6 enabled auto-merge (squash) January 24, 2026 01:34
@efd6 efd6 merged commit 4255f8e into 9.2 Jan 24, 2026
206 of 207 checks passed
@efd6 efd6 deleted the mergify/bp/9.2/pr-48499 branch January 24, 2026 16:14
@efd6 efd6 mentioned this pull request Jan 25, 2026
Merged
5 tasks
brijesh-elastic added a commit to elastic/integrations that referenced this pull request Feb 27, 2026
@brijesh-elastic
qualys_vmdr: require stack versions that include rate limit fix (#17564)
07f808d 
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
@brijesh-elastic @ilyannn
qualys_vmdr: require stack versions that include rate limit fix (#17564)
b7688af 
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
@brijesh-elastic @navnit-elastic
qualys_vmdr: require stack versions that include rate limit fix (elas…
8db77d6 
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@andrewkroh andrewkroh andrewkroh approved these changes

@rdner rdner Awaiting requested review from rdner rdner is a code owner automatically assigned from elastic/elastic-agent-data-plane

@leehinman leehinman Awaiting requested review from leehinman leehinman is a code owner automatically assigned from elastic/elastic-agent-data-plane

Assignees

@efd6 efd6

Labels

backport bugfix conflicts There is a conflict in the backported pull request Filebeat Filebeat Team:Security-Service Integrations Security Service Integrations Team

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@elasticmachine @andrewkroh @efd6