💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
[](https://ci-stats.elastic.co/app/apm/services/beats-ci/transactions/view?rangeFrom=2022-03-08T08:47:20.583Z&rangeTo=2022-03-08T09:07:20.583Z&transactionName=BUILD Beats/beats/PR-{number}&transactionType=job&latencyAggregationType=avg&traceId=168b0d59ef7b2430b9c3a0721f2e8e36&transactionId=cf5739ff69b200d9)

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

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

@mdelapenya seems like the backport bot does not really handle the backports 🤔 ? I checked in the history and found some others that backports were not opened like #30631.

@ChrsMark, I'm afraid the backport-v8.2.0 is not yet available, and likely it points to main since main is 8.2 based. What branch would you need to backport this particular PR to? The backport definitions can be found in

@v1v my goal is to make sure that this PR will make it to 8.2 and since ff for 8.1 has passed already I would expect that backporting to 8.2/8.x is the way to go now. Does this mean that master==8.2 at the moment?

Does this mean that master==8.2 at the moment?

I think so, though I'm not part of the release process for Beats.

As far as I see, you can see those details in:

• https://github.com/elastic/beats/blob/main/libbeat/version/version.go#L21
• CI=true make get-version