x-pack/filebeat/input: add IsPathIn and IsPathInLogsFor helpers and use IsPathInLogsFor in inputs#48719
Merged
efd6 merged 10 commits intoelastic:mainfrom Feb 6, 2026
Merged
x-pack/filebeat/input: add IsPathIn and IsPathInLogsFor helpers and use IsPathInLogsFor in inputs#48719efd6 merged 10 commits intoelastic:mainfrom
efd6 merged 10 commits intoelastic:mainfrom
Conversation
…quest trace destination
…te request trace destination
…alidate request trace destination Also improve trace request validation for size and name presence.
…log.IsPathInLogsFor to validate request trace destination Also improve trace request validation for size and name presence.
…or to validate request trace destination
…or to validate request trace destination
efd6
added
enhancement
Filebeat
botelastic
bot
added
needs_team
Contributor
🤖 GitHub commentsJust comment with:
|
Contributor
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Contributor
Contributor
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
chrisberkhout
approved these changes
Feb 6, 2026
Contributor
chrisberkhout
left a comment
chrisberkhout
left a comment
There was a problem hiding this comment.
Looks good. One linter issue that's worth fixing.
x-pack/filebeat/input/entityanalytics/provider/azuread/fetcher/graph/graph.go
Show resolved
Hide resolved
6 tasks
6 tasks
6 tasks
efd6
added a commit
that referenced
this pull request
Feb 7, 2026
…hInLogsFor helpers and use IsPathInLogsFor in inputs (#48740) * x-pack/filebeat/input: improve log path sanitization for request trace logging (#48719) (cherry picked from commit 2dc4e33) # Conflicts: # docs/reference/filebeat/filebeat-input-cel.md # docs/reference/filebeat/filebeat-input-entity-analytics.md # docs/reference/filebeat/filebeat-input-http_endpoint.md # docs/reference/filebeat/filebeat-input-httpjson.md * remove v9 changelog fragment * remove v9 markdown documentation * add asciidoc documentation * add changelog entry * add missing fmt import --------- Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
rdner
added a commit
that referenced
this pull request
Feb 10, 2026
The old Python-based `docker-compose` CLI is deprecated. All invocations are replaced with the official `docker compose` plugin (Go-based). The current use of `docker-compose` is broken, this is fixing the root cause. Also fixed failing tests on Windows introduced in #48719 Note: * `--force-rm` told the old tool to remove intermediate containers after a build. Docker Compose V2 does this by default (standard Docker build behavior), so the flag was simply removed from all 4 locations. * `--ignore-pull-failures` told the old tool to continue if pulling some images fails. Removed the flag and made the pull non-fatal instead, since the subsequent up command will build images if needed. Assisted by Cursor.
mergify bot
pushed a commit
that referenced
this pull request
Feb 10, 2026
The old Python-based `docker-compose` CLI is deprecated. All invocations are replaced with the official `docker compose` plugin (Go-based). The current use of `docker-compose` is broken, this is fixing the root cause. Also fixed failing tests on Windows introduced in #48719 Note: * `--force-rm` told the old tool to remove intermediate containers after a build. Docker Compose V2 does this by default (standard Docker build behavior), so the flag was simply removed from all 4 locations. * `--ignore-pull-failures` told the old tool to continue if pulling some images fails. Removed the flag and made the pull non-fatal instead, since the subsequent up command will build images if needed. Assisted by Cursor. (cherry picked from commit dfd9525) # Conflicts: # docs/devguide/testing.asciidoc # docs/extend/metricset-details.md
mergify bot
pushed a commit
that referenced
this pull request
Feb 10, 2026
The old Python-based `docker-compose` CLI is deprecated. All invocations are replaced with the official `docker compose` plugin (Go-based). The current use of `docker-compose` is broken, this is fixing the root cause. Also fixed failing tests on Windows introduced in #48719 Note: * `--force-rm` told the old tool to remove intermediate containers after a build. Docker Compose V2 does this by default (standard Docker build behavior), so the flag was simply removed from all 4 locations. * `--ignore-pull-failures` told the old tool to continue if pulling some images fails. Removed the flag and made the pull non-fatal instead, since the subsequent up command will build images if needed. Assisted by Cursor. (cherry picked from commit dfd9525)
mergify bot
pushed a commit
that referenced
this pull request
Feb 10, 2026
The old Python-based `docker-compose` CLI is deprecated. All invocations are replaced with the official `docker compose` plugin (Go-based). The current use of `docker-compose` is broken, this is fixing the root cause. Also fixed failing tests on Windows introduced in #48719 Note: * `--force-rm` told the old tool to remove intermediate containers after a build. Docker Compose V2 does this by default (standard Docker build behavior), so the flag was simply removed from all 4 locations. * `--ignore-pull-failures` told the old tool to continue if pulling some images fails. Removed the flag and made the pull non-fatal instead, since the subsequent up command will build images if needed. Assisted by Cursor. (cherry picked from commit dfd9525)
rdner
added a commit
that referenced
this pull request
Feb 10, 2026
…#48770) The old Python-based `docker-compose` CLI is deprecated. All invocations are replaced with the official `docker compose` plugin (Go-based). The current use of `docker-compose` is broken, this is fixing the root cause. Also fixed failing tests on Windows introduced in #48719 Note: * `--force-rm` told the old tool to remove intermediate containers after a build. Docker Compose V2 does this by default (standard Docker build behavior), so the flag was simply removed from all 4 locations. * `--ignore-pull-failures` told the old tool to continue if pulling some images fails. Removed the flag and made the pull non-fatal instead, since the subsequent up command will build images if needed. Assisted by Cursor. (cherry picked from commit dfd9525) Co-authored-by: Denis <denis.rechkunov@elastic.co>
rdner
added a commit
that referenced
this pull request
Feb 10, 2026
… docker compose (#48768) The old Python-based `docker-compose` CLI is deprecated. All invocations are replaced with the official `docker compose` plugin (Go-based). The current use of `docker-compose` is broken, this is fixing the root cause. Also fixed failing tests on Windows introduced in #48719 Note: * `--force-rm` told the old tool to remove intermediate containers after a build. Docker Compose V2 does this by default (standard Docker build behavior), so the flag was simply removed from all 4 locations. * `--ignore-pull-failures` told the old tool to continue if pulling some images fails. Removed the flag and made the pull non-fatal instead, since the subsequent up command will build images if needed. Assisted by Cursor. (cherry picked from commit dfd9525) # Conflicts: # docs/devguide/testing.asciidoc # docs/extend/metricset-details.md * Delete docs/extend/metricset-details.md * Resolve conflicts --------- Co-authored-by: Denis <denis.rechkunov@elastic.co>
rdner
added a commit
that referenced
this pull request
Feb 10, 2026
…#48769) The old Python-based `docker-compose` CLI is deprecated. All invocations are replaced with the official `docker compose` plugin (Go-based). The current use of `docker-compose` is broken, this is fixing the root cause. Also fixed failing tests on Windows introduced in #48719 Note: * `--force-rm` told the old tool to remove intermediate containers after a build. Docker Compose V2 does this by default (standard Docker build behavior), so the flag was simply removed from all 4 locations. * `--ignore-pull-failures` told the old tool to continue if pulling some images fails. Removed the flag and made the pull non-fatal instead, since the subsequent up command will build images if needed. Assisted by Cursor. (cherry picked from commit dfd9525) Co-authored-by: Denis <denis.rechkunov@elastic.co>
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
See title.
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