#Monitoring SGrid.

1 messages · Page 1 of 1 (latest)

raven bridge
#

I understand it's still in its infancy, but so far from what I've found in the documentation, there is little information on how to add the grid to the pollers.

Additionally, what impact does this additional collection have for sizing the nabox OVA?
My grid is only about 1Pb in size but is used heavily for fabric pool, and with 4 clusters that already push my sad little OVA pretty hard, I'm worried about dropping clusters for monitoring.

strange spindle
#

I wouldn’t think SG monitoring adds a lot capacity wise, or even cpu but I’ll let the harvest people comment.

You’re right there isn’t a lot of documentation regarding SG management in NAbox, that’s because I’m supposed to do that soon but didn’t get around it yet !

raven bridge
strange spindle
#

I’m currently considering major changes for nabox 4 but that’s gonna be a lot of work. I want to finalize 3.4+ first and SG is definitely top of the list

keen meadow
#

Yann's correct. The SG collector won't add much in terms of footprint or CPU. There are many fewer metrics collected in SG than ONTAP

#

And @raven bridge you probably already know this, but a number of folks have been using SG with nabox for a few releases now without issue if you want to try

strange spindle
#

Basically starting with 3.3, you can manually add SG cluster in harvest.yaml

raven bridge
raven bridge
keen meadow
raven bridge
#

True hero

austere sigil
#

I've been monitoring 2 grids for multiple months. Works fine.

strange spindle
raven bridge
#

I just sat down to do this manually today and here we are.
Early Christmas gifts.

austere sigil
#

I upgraded yesterday and it picked up my 2 manually-configured grids into the web ui. See my comments about the grafana upgrade and the config settings in 3.4 though.

raven bridge
#

"an error occurred"
Is there anywhere I can dig out specifically what error this is?

keen meadow
#

@strange spindle may have more ideals but if you can ssh into nabox you should be able to see the logs. Not sure if the text your pasted, "an error occurred" happened in nabox or Harvest. You can check nabox's log files by running dc logs nabox-api and nabox's Harvest logs by running dc logs nabox-harvest2 if you don't see anything feel free to tar them up and send them to us and we can take a look https://netapp.github.io/harvest/23.11/help/log-collection/#nabox email address is ng-harvest-files@netapp.com

raven bridge
#

I managed to resolve it, it did not like DNS for some reason, something for me to dig around with.

strange spindle
#

I noticed the network settings in NAbox kind of forget domain name sometimes, that would prevent you to use short names to add systems, maybe that's it ?

#

I thought I was doing a better job reporting errors, looks like I still have work to do 😄 It would help if you find out exactly what the problem was