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

nfs: add support for nfs-ganesha metrics monitoring #12007

Merged
merged 1 commit into from
Apr 4, 2023

Conversation

synarete
Copy link
Contributor

NFS-Ganesha (as of V5-dev.2 [1]) supports Prometheus monitoring from within the NFS server itself. It provides metrics for both connected clients and active exports, via TCP port 9587. Expose those metrics via standard K8S service.

[1] nfs-ganesha/nfs-ganesha@b6c59df

Description of your changes:

Which issue is resolved by this Pull Request:
Resolves #

Checklist:

  • Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide).
  • Skip Tests for Docs: If this is only a documentation change, add the label skip-ci on the PR.
  • Reviewed the developer guide on Submitting a Pull Request
  • Pending release notes updated with breaking and/or notable changes for the next minor release.
  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • Integration tests have been added, if necessary.

NFS-Ganesha (as of V5-dev.2 [1]) supports Prometheus monitoring from
within the NFS server itself. It provides metrics for both connected
clients and active exports, via TCP port 9587. Expose those metrics via
existing nfs k8s-service.

[1] nfs-ganesha/nfs-ganesha@b6c59df

Signed-off-by: Shachar Sharon <ssharon@redhat.com>
@BlaineEXE BlaineEXE merged commit 822c56f into rook:master Apr 4, 2023
48 of 50 checks passed
travisn added a commit that referenced this pull request Apr 4, 2023
nfs: add support for nfs-ganesha metrics monitoring (backport #12007)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants