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

[GCP] Update fields docs and fix inconsistencies after #27974 #33006

Merged
merged 10 commits into from
Sep 14, 2022

Conversation

endorama
Copy link
Member

@endorama endorama commented Sep 7, 2022

What does this PR do?

Update the wording in different GCP metricsets about metrics name not being changed from their original GCP counterparts, as they have been updated in #27974 to align them with Beats naming conventions.

Remove fields names and description as they are available through exported fields section, which is automatically updated from fields definitions and don't risk being outdated.

Why is it important?

Documentation was confusing and not helping users.

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.

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

After we aligned metrics with Beats naming convention (elastic#27974)
the docs has not been adequately updated.
@endorama endorama requested a review from a team as a code owner September 7, 2022 09:33
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Sep 7, 2022
@endorama endorama added backport-7.17 Automated backport to the 7.17 branch with mergify Team:Cloud-Monitoring Label for the Cloud Monitoring team backport-v8.4.0 Automated backport with mergify labels Sep 7, 2022
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Sep 7, 2022
@elasticmachine
Copy link
Collaborator

elasticmachine commented Sep 7, 2022

💚 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: 2022-09-09T08:09:01.002+0000

  • Duration: 7 min 21 sec

❕ Flaky test report

No test was executed to be analysed.

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

@endorama endorama force-pushed the gcp-fields-docs-fixes branch from b7d5a33 to f771e0c Compare September 7, 2022 10:21
Copy link
Contributor

@dedemorton dedemorton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested some fixes to the asciidoc tagging. Let me know if you need help with the list formatting. There are some other tricks I know that aren't covered in the readme.

@@ -1,96 +1,30 @@
Compute metricset to fetch metrics from https://cloud.google.com/compute/[Compute Engine] Virtual Machines in Google Cloud Platform. No Monitoring or Logging agent is required in your instances to use this metricset.

The `compute` metricset contains all metrics exported from the https://cloud.google.com/monitoring/api/metrics_gcp#gcp-compute[Stackdriver API]. The field names have been left untouched for people already familiar with them.
The `compute` metricset contains all metrics exported from the https://cloud.google.com/monitoring/api/metrics_gcp#gcp-compute[Stackdriver API]. The field names are aligned to https://www.elastic.co/guide/en/beats/devguide/current/event-conventions.html[Beats naming conventions] with minor modifications to their GCP metrics name counterpart.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The `compute` metricset contains all metrics exported from the https://cloud.google.com/monitoring/api/metrics_gcp#gcp-compute[Stackdriver API]. The field names are aligned to https://www.elastic.co/guide/en/beats/devguide/current/event-conventions.html[Beats naming conventions] with minor modifications to their GCP metrics name counterpart.
The `compute` metricset contains all metrics exported from the https://cloud.google.com/monitoring/api/metrics_gcp#gcp-compute[Stackdriver API]. The field names are aligned to {beats-devguide}/event-conventions.html[Beats naming conventions] with minor modifications to their GCP metrics name counterpart.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

avoid hard coding doc paths. Note that the path attributes you can use are defined here: https://github.com/elastic/docs/blob/master/shared/attributes.asciidoc

=== Metrics and labels
Here is a list of metrics collected by `compute` metricset:
=== Labels
Here is a list of labels collected by `compute` metricset depending on the type of metric being collected:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Here is a list of labels collected by `compute` metricset depending on the type of metric being collected:
Here is a list of labels collected by the `compute` metricset depending on the type of metric being collected:

x-pack/metricbeat/module/gcp/dataproc/_meta/docs.asciidoc Outdated Show resolved Hide resolved
x-pack/metricbeat/module/gcp/firestore/_meta/docs.asciidoc Outdated Show resolved Hide resolved
x-pack/metricbeat/module/gcp/gke/_meta/docs.asciidoc Outdated Show resolved Hide resolved
x-pack/metricbeat/module/gcp/storage/_meta/docs.asciidoc Outdated Show resolved Hide resolved
x-pack/metricbeat/module/gcp/storage/_meta/docs.asciidoc Outdated Show resolved Hide resolved
x-pack/metricbeat/module/gcp/compute/_meta/docs.asciidoc Outdated Show resolved Hide resolved
x-pack/metricbeat/module/gcp/compute/_meta/docs.asciidoc Outdated Show resolved Hide resolved
@endorama endorama requested a review from dedemorton September 9, 2022 08:39
Copy link
Contributor

@dedemorton dedemorton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@endorama endorama merged commit 923e11f into elastic:main Sep 14, 2022
@endorama endorama deleted the gcp-fields-docs-fixes branch September 14, 2022 12:40
mergify bot pushed a commit that referenced this pull request Sep 14, 2022
Co-authored-by: DeDe Morton <[email protected]>
(cherry picked from commit 923e11f)

# Conflicts:
#	x-pack/metricbeat/module/gcp/dataproc/_meta/docs.asciidoc
#	x-pack/metricbeat/module/gcp/firestore/_meta/docs.asciidoc
mergify bot pushed a commit that referenced this pull request Sep 14, 2022
endorama added a commit that referenced this pull request Sep 15, 2022
…es after #27974 (#33080)

Co-authored-by: DeDe Morton <[email protected]>
Co-authored-by: Edoardo Tenani <[email protected]>
endorama added a commit that referenced this pull request Sep 19, 2022
…ies after #27974 (#33079)

Co-authored-by: DeDe Morton <[email protected]>
Co-authored-by: Edoardo Tenani <[email protected]>
Co-authored-by: Edoardo Tenani <[email protected]>
chrisberkhout pushed a commit that referenced this pull request Jun 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-7.17 Automated backport to the 7.17 branch with mergify backport-v8.4.0 Automated backport with mergify Team:Cloud-Monitoring Label for the Cloud Monitoring team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants