Hello,
Harvest now include a StorageGRID collector.
Is the support of StorageGrid planned in NABOX roadmap ?
Best Regards,
#StorageGrid support in NAbox
gritty oak
chrome hornet
It’s on the todo !
pulsar mantle
@gritty oak in the meantime, we can walk you through the steps to add it manually if you don't want to wait
muted hedge
It’s on the todo !
ETA? weeks? months? I imagine that your todo list is likely longer than the time you have to work on it.
rancid glade
Yeh would like to see this too
gritty oak
<@1051972040908877856> in the meantime, we can walk you through the steps to add...
Gladly if you can tell me the manual procedure in the meantime.
pulsar mantle
@chrome hornet do you already have documented how to edit nabox's harvest.yml?
chrome hornet
I’m afraid not. Manuel changes might work but there is a good chance it’ll break either during reading or writing. I’ll do some research.
pulsar mantle
thanks! would be a nice stopgap while there is a gap between Nabox and Harvest
chrome hornet
Yes I’ll make something for next release
chrome hornet
All right, so 3.3b1 should behave much better regarding "foreign" entries in harvest.yaml. You should be able to put your StorageGrid and it'll even show in the UI
GA will have full UI implementation
pulsar mantle
@gritty oak with @chrome hornet 's changes mentioned above. You can add a StorageGRID poller by editing your harvest.yml file on nabox. Do that by sshing into your nabox instance and editing /opt/harvest2-conf/harvest.yml Add a new poller as mentioned here https://netapp.github.io/harvest/22.11/configure-storagegrid/ and make sure the storagegrid user has the appropriate permissions as mentioned here https://netapp.github.io/harvest/22.11/prepare-storagegrid-clusters/ Here's an example poller definition:
sg-tmp:
datacenter: rtp
addr: 10.1.1.1
use_insecure_tls: true
username: user
password: pass
collectors:
- StorageGrid
exporters:
- prometheus1
chrome hornet
one comment, you must add prometheus_port also, make sure you use one that is not used in another definition. You might have to allow unsecure TLS
pulsar mantle
does nabox do something with prometheus_port ? I'm asking because Harvest does not
the port is handled by the exporter (in the example above, prometheus1 defines the exporter, port, etc.) And yes, use_insecure_tls: true may be required
chrome hornet
That's a good point. How it works currently is NAbox reads harvest.yaml and extracts prometheus_port to add it in the arguments when launching poller process