[9.1](backport #45145) [beatreceivers] Introduce otel mode for metricbeat#45312
[9.1](backport #45145) [beatreceivers] Introduce otel mode for metricbeat#45312khushijain21 merged 2 commits into9.1from
Conversation
* [beatreceivers] Introduce otel mode for metricbeat (cherry picked from commit f0b0f2a) # Conflicts: # x-pack/libbeat/common/otelbeat/otel.go
|
Cherry-pick of f0b0f2a has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
@khushijain21 could you please fix the conflicts? |
| defer metricbeat.Stop() | ||
|
|
||
| // prepare to query ES | ||
| es := integration.GetESClient(t, "http") |
There was a problem hiding this comment.
@khushijain21 I'm not sure how this managed to pass CI checks, this function is not present on 9.1 :/
There was a problem hiding this comment.
that is very strange because the build did fail the stage did not
There was a problem hiding this comment.
oh now I know - the mage command does not check if the main integ test failed or not. I will update the code. Thanks @mauri870
Proposed commit message
This PR introduces otel mode for metricbeat. This will allow us to write e2e test for metricbeat inputs.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
Tests:
This is an automatic backport of pull request #45145 done by [Mergify](https://mergify.com).