Skip to content

otel: update filebeat integration tests to run in isolation #45314

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jul 11, 2025
Merged

otel: update filebeat integration tests to run in isolation #45314

merged 1 commit into from
Jul 11, 2025

Conversation

mauri870
Copy link
Member

@mauri870 mauri870 commented Jul 10, 2025 •
edited
Loading

Proposed commit message

As a leftover from #45093, the tests added reuse the index names which may cause issues when running the tests in sequence without cleaning up first. Additionally, the beats receivers should not use the same path.home.

Adjusted the existing tests to use unique indexes and individual home folders.

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
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

@mauri870
otel: update filebeat integration tests to run in isolation
c0bd76e 
As a leftover from elastic#45093, the
tests added reuse the index names which may cause issues when running
the tests in sequence without cleaning up first.

Adjusted the existing tests to use unique indexes.
@mauri870 mauri870 self-assigned this Jul 10, 2025
@mauri870 mauri870 added cleanup Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Jul 10, 2025
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Jul 10, 2025
@github-actions GitHub Actions
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

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

@mergify Mergify
Copy link
Contributor

mergify bot commented Jul 10, 2025

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @mauri870? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@mauri870 mauri870 added backport-active-9 Automated backport with mergify to all the active 9.[0-9]+ branches backport-8.19 Automated backport to the 8.19 branch labels Jul 10, 2025
@mauri870 mauri870 mentioned this pull request Jul 10, 2025
Merged
6 tasks
@mauri870 mauri870 marked this pull request as ready for review July 10, 2025 19:46
@mauri870 mauri870 requested a review from a team as a code owner July 10, 2025 19:46
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@khushijain21
Copy link
Contributor

LGTM!

@mauri870 mauri870 merged commit ea98564 into elastic:main Jul 11, 2025
37 checks passed
@github-actions GitHub Actions
Copy link
Contributor

@Mergifyio backport 9.0 9.1

@mergify Mergify
Copy link
Contributor

mergify bot commented Jul 11, 2025 •
edited
Loading

backport 9.0 9.1

✅ Backports have been created

@mauri870 mauri870 added this to the otel milestone Jul 11, 2025
mergify bot pushed a commit that referenced this pull request Jul 11, 2025
@mauri870 @mergify
otel: update filebeat integration tests to run in isolation (#45314)
5043e5e 
As a leftover from #45093, the
tests added reuse the index names which may cause issues when running
the tests in sequence without cleaning up first.

Adjusted the existing tests to use unique indexes.

(cherry picked from commit ea98564)

# Conflicts:
#	x-pack/filebeat/tests/integration/otel_test.go
mergify bot pushed a commit that referenced this pull request Jul 11, 2025
@mauri870 @mergify
otel: update filebeat integration tests to run in isolation (#45314)
b47fefe 
As a leftover from #45093, the
tests added reuse the index names which may cause issues when running
the tests in sequence without cleaning up first.

Adjusted the existing tests to use unique indexes.

(cherry picked from commit ea98564)

# Conflicts:
#	x-pack/filebeat/tests/integration/otel_test.go
mergify bot pushed a commit that referenced this pull request Jul 11, 2025
@mauri870 @mergify
otel: update filebeat integration tests to run in isolation (#45314)
0867713 
As a leftover from #45093, the
tests added reuse the index names which may cause issues when running
the tests in sequence without cleaning up first.

Adjusted the existing tests to use unique indexes.

(cherry picked from commit ea98564)
This was referenced Jul 11, 2025
Closed
Closed
Merged
mauri870 added a commit that referenced this pull request Jul 11, 2025
@mergify @mauri870
otel: update filebeat integration tests to run in isolation (#45314) (#…
d7344de 
…45319)

As a leftover from #45093, the
tests added reuse the index names which may cause issues when running
the tests in sequence without cleaning up first.

Adjusted the existing tests to use unique indexes.

(cherry picked from commit ea98564)

Co-authored-by: Mauri de Souza Meneguzzo <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@khushijain21 khushijain21 khushijain21 approved these changes

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

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

Assignees

@mauri870 mauri870

Labels
backport-8.19 Automated backport to the 8.19 branch backport-active-9 Automated backport with mergify to all the active 9.[0-9]+ branches cleanup Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Milestone
otel
Development

Successfully merging this pull request may close these issues.
3 participants
@mauri870 @elasticmachine @khushijain21