chore: update github.com/prometheus/prometheus to v0.312.0#51915
Conversation
``` go get github.com/prometheus/prometheus@v0.312.0 go mod tidy make notice ```
botelastic
Bot
added
the
needs_team
🤖 GitHub commentsJust comment with:
|
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
andrzej-stencel
added
skip-changelog
Team:Elastic-Agent-Data-Plane
botelastic
Bot
removed
the
needs_team
andrzej-stencel
added
the
backport-active-all
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
This comment has been minimized.
This comment has been minimized.
TL;DRThe Buildkite failure is an isolated Python integration-test timeout in x-pack/filebeat/tests/system/test_xpack_modules.py::XPackTest::test_fileset_file_109_cisco. The test waited 20 seconds for the Elasticsearch index for x-pack/filebeat/module/cisco/ftd/test/filtered.log; the captured output reports Beat had no output file. This is not tied to the PR changed files, which are dependency metadata only. Remediation
Investigation detailsRoot CauseThe failure occurs after Filebeat is run with the cisco/ftd module and filtered.log. filebeat/tests/system/test_modules.py:295-297 waits for the test index after the process run; the timeout is raised by libbeat/tests/system/beat/beat.py:433-454. The failure log shows no Filebeat output, so the available evidence does not identify a parser or dependency regression. Evidence
Verification
What is this? | From workflow: PR Buildkite Detective Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. |
|
Tick the box to add this pull request to the merge queue (same as
|
|
@Mergifyio backport 9.5 9.4 9.3 8.19 |
✅ Backports have been createdDetails
|
2 participants
Checklist
[ ] 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 thestresstest.shscript to run them under stress conditions and race detector to verify their stability.[ ] I have added an entry in./changelog/fragmentsusing the changelog tool.