I'm not sure if this forum is meant to be just for the NAbox embedding of Harvest or if general Harvest questions are welcome. I'll delete if they're not. But before I put up an issue on GitHub, is there a reason why things like status/operational state/etc. aren't present (other than just not being written yet)?
#Active/enabled/up boolean metrics
stoic narwhal
novel yew
hi @stoic narwhal Harvest questions are welcome here. Which metric in particular are you asking about?
stoic narwhal
It's the lack of particular metrics rather than any existing metric
E.g. there's a node_uptime, but no node_admin_state or node_operational_state
Not just for node_*, but for any "thing" that can be up/down, active/inactive, etc.
Some sort of "boolean" metric that's 1 if the thing is up and 0 if it's down
novel yew
take a look at https://netapp.github.io/harvest/nightly/ontap-metrics/#node_new_status typically we export *_new_status metrics for that sort of information. If you search on this page, you'll see the full list of them https://netapp.github.io/harvest/nightly/ontap-metrics
stoic narwhal
Oh, I see now
May I ask why new is in the name rather than node_status?
(just curious)
novel yew
good question! It's because some objects already export a _status metric and we needed a way to disambiguate them
stoic narwhal
Alright then, lol
novel yew
lol indeed. It's one of those things we would change if we could, but it would be more inconsiderate to change the name of metrics now
stoic narwhal
Yeah, it's the kind of thing you really only get one shot at, and there's a bit of a linguistic quagmire around state/status/operational status/active/enabled/etc/etc, and I don't necessarily have a better name in mind
But I did see and skim over them and assumed they had something to do with newly-added or perhaps uninitialized status
novel yew
yep that makes sense. Hopefully the public docs I shared make sense
stoic narwhal
They do, thank you
novel yew
you're welcome!