beats icon indicating copy to clipboard operation
beats copied to clipboard

Update documentation to use ingest_pipeline metricset

Open laraMorenoIgle opened this issue 2 years ago • 6 comments

As confirmed by Dev in this comment https://github.com/elastic/sdh-beats/issues/4050#issuecomment-1808008624 the metricset name for collecting elasticsearch ingest data should be ingest_pipeline and not ingest.

Proposed commit message

Update configuration example for ingest_pipeline metricset so it includes the right name, since it was wrongly name ingest instead of ingest_pipeline.

laraMorenoIgle avatar Nov 13 '23 12:11 laraMorenoIgle

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

botelastic[bot] avatar Nov 13 '23 12:11 botelastic[bot]

This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @laraMorenoIgle? 🙏. 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-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

mergify[bot] avatar Nov 13 '23 12:11 mergify[bot]

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-11-13T12:11:38.276+0000

  • Duration: 8 min 28 sec

:grey_exclamation: Flaky test report

No test was executed to be analysed.

:robot: GitHub comments

Expand to view the 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!)

elasticmachine avatar Nov 13 '23 12:11 elasticmachine

This pull request does not have a backport label. If this is a bug or security fix, could you label this PR @laraMorenoIgle? 🙏. 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-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

mergify[bot] avatar Feb 05 '24 14:02 mergify[bot]

backport-8.x has been added to help with the transition to the new branch 8.x. If you don't need it please use backport-skip label and remove the backport-8.x label.

mergify[bot] avatar Dec 26 '24 19:12 mergify[bot]

This pull request is now in conflicts. Could you fix it? 🙏 To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b laraMorenoIgle-patch-1 upstream/laraMorenoIgle-patch-1
git merge upstream/main
git push upstream laraMorenoIgle-patch-1

mergify[bot] avatar Dec 08 '25 07:12 mergify[bot]