-
Notifications
You must be signed in to change notification settings - Fork 204
Fix tests in preparation for making otel self monitoring default #10537
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
Merged
Conversation
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
Contributor
💛 Build succeeded, but was flaky
Failed CI Stepscc @swiatekm |
cmacknz
reviewed
Oct 14, 2025
cmacknz
approved these changes
Oct 14, 2025
Contributor
|
@Mergifyio backport 8.18 8.19 9.0 9.1 9.2 |
Contributor
✅ Backports have been createdDetails
|
mergify bot
pushed a commit
that referenced
this pull request
Oct 14, 2025
) * Fix leak integration test * Improve detection of agent processes in integration tests * Explicitly set the runtime in monitoring integration test * Make the check for component metrics more generic * Check the right build hash in integration tests (cherry picked from commit 3ccf28d) # Conflicts: # testing/integration/ess/beat_receivers_test.go # testing/integration/ess/metrics_monitoring_test.go
Closed
5 tasks
mergify bot
pushed a commit
that referenced
this pull request
Oct 14, 2025
) * Fix leak integration test * Improve detection of agent processes in integration tests * Explicitly set the runtime in monitoring integration test * Make the check for component metrics more generic * Check the right build hash in integration tests (cherry picked from commit 3ccf28d) # Conflicts: # testing/integration/ess/metrics_monitoring_test.go
Merged
5 tasks
mergify bot
pushed a commit
that referenced
this pull request
Oct 14, 2025
) * Fix leak integration test * Improve detection of agent processes in integration tests * Explicitly set the runtime in monitoring integration test * Make the check for component metrics more generic * Check the right build hash in integration tests (cherry picked from commit 3ccf28d) # Conflicts: # testing/integration/ess/beat_receivers_test.go
Closed
5 tasks
mergify bot
pushed a commit
that referenced
this pull request
Oct 14, 2025
) * Fix leak integration test * Improve detection of agent processes in integration tests * Explicitly set the runtime in monitoring integration test * Make the check for component metrics more generic * Check the right build hash in integration tests (cherry picked from commit 3ccf28d)
Merged
5 tasks
mergify bot
pushed a commit
that referenced
this pull request
Oct 14, 2025
) * Fix leak integration test * Improve detection of agent processes in integration tests * Explicitly set the runtime in monitoring integration test * Make the check for component metrics more generic * Check the right build hash in integration tests (cherry picked from commit 3ccf28d)
Merged
5 tasks
swiatekm
added a commit
that referenced
this pull request
Oct 14, 2025
) (#10552) * Fix leak integration test * Improve detection of agent processes in integration tests * Explicitly set the runtime in monitoring integration test * Make the check for component metrics more generic * Check the right build hash in integration tests (cherry picked from commit 3ccf28d) Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com>
swiatekm
added a commit
that referenced
this pull request
Oct 14, 2025
) (#10553) * Fix leak integration test * Improve detection of agent processes in integration tests * Explicitly set the runtime in monitoring integration test * Make the check for component metrics more generic * Check the right build hash in integration tests (cherry picked from commit 3ccf28d) Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com>
swiatekm
added a commit
that referenced
this pull request
Oct 15, 2025
…f monitoring default (#10550) * Fix tests in preparation for making otel self monitoring default (#10537) * Fix leak integration test * Improve detection of agent processes in integration tests * Explicitly set the runtime in monitoring integration test * Make the check for component metrics more generic * Check the right build hash in integration tests (cherry picked from commit 3ccf28d) # Conflicts: # testing/integration/ess/metrics_monitoring_test.go * Fix conflicts --------- Co-authored-by: Mikołaj Świątek <mail@mikolajswiatek.com>
hayotbisonai
pushed a commit
to hayotbisonai/elastic-agent
that referenced
this pull request
Nov 23, 2025
…stic#10537) * Fix leak integration test * Improve detection of agent processes in integration tests * Explicitly set the runtime in monitoring integration test * Make the check for component metrics more generic * Check the right build hash in integration tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport-active-all
Automated backport with mergify to all the active branches
chore
Tasks that just need to be done, they are neither bug, nor enhancements
skip-changelog
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.
What does this PR do?
Fixes tests which implicitly assume beats are running as processes as opposed to otel receivers. More specifically:
Why is it important?
We want to enable beats receivers for self-monitoring by default. This PR makes the test adjustments separately to show they all pass for beats processes as well.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added an entry in./changelog/fragmentsusing the changelog toolRelated issues