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

Please add "Suspended" as a node_zfs_zpool_state #2421

Closed
Hooloovoo opened this issue Jul 11, 2022 · 2 comments · Fixed by #2449
Closed

Please add "Suspended" as a node_zfs_zpool_state #2421

Hooloovoo opened this issue Jul 11, 2022 · 2 comments · Fixed by #2449

Comments

@Hooloovoo
Copy link

Hello,

It is great that the node_exporter collects node_zfs_zpool_state. It currently has:
unavail
degraded
faulted
offline
online
removed

var zfsPoolStatesName = []string{"online", "degraded", "faulted", "offline", "removed", "unavail"}

I had a pool that was in the "SUSPENDED" state:
$ zpool status
pool: [pool name]
state: SUSPENDED
status: One or more devices are faulted in response to IO failures.
action: Make sure the affected devices are connected, then run 'zpool clear'.
see: http://zfsonlinux.org/msg/ZFS-8000-HC

and so none of the above statuses were triggered (thankfully I also monitor for online != 1). Could you please add this status as well?

Host operating system: output of uname -a

Linux mythbuntu-server 5.4.0-121-generic #137-Ubuntu SMP Wed Jun 15 13:33:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

node_exporter version: output of node_exporter --version

n/a -- I am using Grafana agent, but they say:
grafana/agent#1854
that they are importing you directly as an upstream.

Are you running node_exporter in Docker?

No.

@conallob
Copy link
Contributor

I would like to work on this, unless there is already someone actively working on it

@SuperQ
Copy link
Member

SuperQ commented Apr 26, 2023

@conallob Looks like there's already an open PR for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants