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

MON-3113: add nodeExporter.collectors.mountstats settings. #1936

Merged
merged 2 commits into from Jun 19, 2023

Conversation

raptorsun
Copy link
Contributor

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 5, 2023
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 5, 2023

@raptorsun: This pull request references MON-3113 which is a valid jira issue.

In response to this:

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 5, 2023
@openshift-ci openshift-ci bot requested review from slashpai and sthaha April 5, 2023 10:09
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 5, 2023
@raptorsun raptorsun force-pushed the feature/MON-3113 branch 2 times, most recently from e6d3db4 to 320919f Compare April 6, 2023 10:14
@raptorsun raptorsun changed the title [WIP] MON-3113: add nodeExporter.collectors.mountstats settings. MON-3113: add nodeExporter.collectors.mountstats settings. Apr 11, 2023
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 11, 2023
@raptorsun
Copy link
Contributor Author

/retest

@raptorsun
Copy link
Contributor Author

/retest-required

1 similar comment
@raptorsun
Copy link
Contributor Author

/retest-required

@raptorsun raptorsun force-pushed the feature/MON-3113 branch 2 times, most recently from 8c87a93 to 71df1c8 Compare April 24, 2023 17:17
@Tai-RedHat
Copy link

test PR with cluster-bot, but I can not find the following metrics after enabling mountstats

1. node_mountstats_nfs_read_bytes_total
2. node_mountstats_nfs_write_bytes_total
3. node_mountstats_nfs_operations_requests_total

Is it necessary to attach NFS pv to see the metrics?

// `node_mountstats_nfs_operations_requests_total`.
//
// Please be aware that these metric can have a high cardinality.
// If you enable this collector, watch the prometheus-k8s deployment closely for excessive memory usage.
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
// If you enable this collector, watch the prometheus-k8s deployment closely for excessive memory usage.
// If you enable this collector, monitor closely any increase of the memory usage for the prometheus-k8s pods.

@raptorsun
Copy link
Contributor Author

test PR with cluster-bot, but I can not find the following metrics after enabling mountstats

1. node_mountstats_nfs_read_bytes_total
2. node_mountstats_nfs_write_bytes_total
3. node_mountstats_nfs_operations_requests_total

Is it necessary to attach NFS pv to see the metrics?

Yes, it is necessary to have an NFS volume mounted on the host to see these metrics.

Copy link
Contributor

@simonpasquier simonpasquier left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 1, 2023
@Tai-RedHat
Copy link

test PR with cluster-bot, but I can not find the following metrics after enabling mountstats

1. node_mountstats_nfs_read_bytes_total
2. node_mountstats_nfs_write_bytes_total
3. node_mountstats_nfs_operations_requests_total

Is it necessary to attach NFS pv to see the metrics?

Yes, it is necessary to have an NFS volume mounted on the host to see these metrics.

Use cluster-bot test again, able to see above metrics.
/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jun 2, 2023
@raptorsun
Copy link
Contributor Author

/retest-required

@raptorsun
Copy link
Contributor Author

Hello @bburt-rh @Senthamilarasu-STA, could you please have a look and stamp it with labels "docs-approved" and "px-approved"? Thanks :)

@simonpasquier
Copy link
Contributor

/skip

@simonpasquier
Copy link
Contributor

/retest-required

pkg/manifests/types.go Outdated Show resolved Hide resolved
pkg/manifests/types.go Outdated Show resolved Hide resolved
pkg/manifests/types.go Outdated Show resolved Hide resolved
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 7, 2023
@raptorsun
Copy link
Contributor Author

Thank you @bburt-rh :D I have updated the documentation accordingly. Could you please review it again?

@bburt-rh
Copy link
Contributor

bburt-rh commented Jun 7, 2023

/label docs-approved

@openshift-ci openshift-ci bot added the docs-approved Signifies that Docs has signed off on this PR label Jun 7, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 7, 2023

@raptorsun: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-single-node fc6435a link false /test e2e-aws-ovn-single-node
ci/prow/versions fc6435a link false /test versions

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@danielmellado
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 8, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 8, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danielmellado, raptorsun, simonpasquier

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [raptorsun,simonpasquier]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit 9a4dd37 into openshift:master Jun 19, 2023
14 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. docs-approved Signifies that Docs has signed off on this PR jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants