Skip to content
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

[8.x](backport #42226) [filebeat] Add E2E testing for filebeat in otel mode #42276

Merged
merged 1 commit into from
Jan 9, 2025
Merged

[8.x](backport #42226) [filebeat] Add E2E testing for filebeat in otel mode #42276

merged 1 commit into from
Jan 9, 2025
+121 −10

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 9, 2025

Proposed commit message

This adds. E2E test for filebeat in otel mode and confirms all the log records are indexed.

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.

How to test this PR locally

cd x-pack/filebeat
mage build
mage docker:composeUp
go test -run TestFilebeatOTelE2E -tags integration ./tests/integration

Related issues

Related to https://github.com/elastic/ingest-dev/issues/4595

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

@khushijain21 @mergify
[filebeat] Add E2E testing for filebeat in otel mode (#42226)
9a8cc52 
* [filebeat] Add E2E testing for filebeat in otel mode

- Add E2E test for filebeat and elasticsearch

Co-authored-by: Denis <denis@rdner.de>

* use v8 es version

* check for existence of events

---------

Co-authored-by: Denis <denis@rdner.de>
(cherry picked from commit e22f933)
@mergify mergify bot requested a review from a team as a code owner January 9, 2025 12:47
@mergify mergify bot added the backport label Jan 9, 2025
@mergify mergify bot requested a review from a team as a code owner January 9, 2025 12:47
@mergify mergify bot requested review from belimawr and leehinman and removed request for a team January 9, 2025 12:47
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 9, 2025
@botelastic
Copy link

botelastic bot commented Jan 9, 2025

This pull request doesn't have a Team:<team> label.

@khushijain21 khushijain21 enabled auto-merge (squash) January 9, 2025 12:53
@khushijain21 khushijain21 merged commit 12bca23 into 8.x Jan 9, 2025
141 checks passed
@khushijain21 khushijain21 deleted the mergify/bp/8.x/pr-42226 branch January 9, 2025 14:28
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

@belimawr belimawr Awaiting requested review from belimawr belimawr 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

@khushijain21 khushijain21

Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@khushijain21