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.

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

[8.0](backport #30008) [Metricbeat] gcp: add dataproc metricset #30332

Closed
wants to merge 1 commit into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 10, 2022

This is an automatic backport of pull request #30008 done by Mergify.
Cherry-pick of e61173f has failed:

On branch mergify/bp/8.0/pr-30008
Your branch is up to date with 'origin/8.0'.

You are currently cherry-picking commit e61173f979.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   CHANGELOG-developer.next.asciidoc
	new file:   metricbeat/docs/modules/gcp/dataproc.asciidoc
	new file:   x-pack/metricbeat/module/gcp/dataproc/_meta/data.json
	new file:   x-pack/metricbeat/module/gcp/dataproc/_meta/data_cluster.json
	new file:   x-pack/metricbeat/module/gcp/dataproc/_meta/docs.asciidoc
	new file:   x-pack/metricbeat/module/gcp/dataproc/_meta/fields.yml
	new file:   x-pack/metricbeat/module/gcp/dataproc/dataproc_integration_test.go
	new file:   x-pack/metricbeat/module/gcp/dataproc/dataproc_test.go
	new file:   x-pack/metricbeat/module/gcp/dataproc/manifest.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   metricbeat/docs/fields.asciidoc
	both modified:   metricbeat/docs/modules/gcp.asciidoc
	both modified:   metricbeat/docs/modules_list.asciidoc
	both modified:   x-pack/metricbeat/metricbeat.reference.yml
	both modified:   x-pack/metricbeat/module/gcp/_meta/config.yml
	both modified:   x-pack/metricbeat/module/gcp/constants.go
	both modified:   x-pack/metricbeat/module/gcp/fields.go
	both modified:   x-pack/metricbeat/module/gcp/metrics/metrics_requester.go
	both modified:   x-pack/metricbeat/module/gcp/metrics/response_parser.go
	both modified:   x-pack/metricbeat/module/gcp/module.yml
	both modified:   x-pack/metricbeat/modules.d/gcp.yml.disabled

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

* Add dataproc metricset

* Update metricbeat docs

(cherry picked from commit e61173f)

# Conflicts:
#	metricbeat/docs/fields.asciidoc
#	metricbeat/docs/modules/gcp.asciidoc
#	metricbeat/docs/modules_list.asciidoc
#	x-pack/metricbeat/metricbeat.reference.yml
#	x-pack/metricbeat/module/gcp/_meta/config.yml
#	x-pack/metricbeat/module/gcp/constants.go
#	x-pack/metricbeat/module/gcp/fields.go
#	x-pack/metricbeat/module/gcp/metrics/metrics_requester.go
#	x-pack/metricbeat/module/gcp/metrics/response_parser.go
#	x-pack/metricbeat/module/gcp/module.yml
#	x-pack/metricbeat/modules.d/gcp.yml.disabled
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Feb 10, 2022
@mergify mergify bot assigned gpop63 Feb 10, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 10, 2022
@botelastic
Copy link

botelastic bot commented Feb 10, 2022

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

@elasticmachine
Copy link
Collaborator

💔 Build Failed

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: 2022-02-10T10:28:55.049+0000

  • Duration: 21 min 35 sec

Test stats 🧪

Test Results
Failed 0
Passed 3
Skipped 0
Total 3

Steps errors 3

Expand to view the steps failures

metricbeat-lint - make -C metricbeat check;make -C metricbeat update;make -C x-pack/metricbeat che
  • Took 2 min 5 sec . View more details here
  • Description: make -C metricbeat check;make -C metricbeat update;make -C x-pack/metricbeat check;make -C x-pack/metricbeat update;make check-no-changes;
x-pack/metricbeat-lint - make -C x-pack/metricbeat check;make -C x-pack/metricbeat update;make -C
  • Took 1 min 35 sec . View more details here
  • Description: make -C x-pack/metricbeat check;make -C x-pack/metricbeat update;make -C metricbeat check;make -C metricbeat update;make check-no-changes;
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error 'hudson.AbortException: script returned exit code 2'

💚 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!)

@mergify
Copy link
Contributor Author

mergify bot commented Feb 14, 2022

This pull request has not been merged yet. Could you please review and merge it @gpop63? 🙏

4 similar comments
@mergify
Copy link
Contributor Author

mergify bot commented Feb 21, 2022

This pull request has not been merged yet. Could you please review and merge it @gpop63? 🙏

@mergify
Copy link
Contributor Author

mergify bot commented Feb 28, 2022

This pull request has not been merged yet. Could you please review and merge it @gpop63? 🙏

@mergify
Copy link
Contributor Author

mergify bot commented Mar 7, 2022

This pull request has not been merged yet. Could you please review and merge it @gpop63? 🙏

@mergify
Copy link
Contributor Author

mergify bot commented Mar 14, 2022

This pull request has not been merged yet. Could you please review and merge it @gpop63? 🙏

@jsoriano
Copy link
Member

@endorama

@jsoriano jsoriano closed this Mar 15, 2022
@mergify mergify bot deleted the mergify/bp/8.0/pr-30008 branch March 15, 2022 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants