Health Checks for Taking on a SolarWinds setup?

Question

If you were to take on (or better yet already have) someone else's SolarWinds environment, then what health checks or indeed, any other kind of checks, would you undertake? I am aware of Active Diagnostics and also the My Deployment Health tab, but do you have a set checklist or alternative approach?

If so, please do share?

TIA.

stuartd · Answer

It definitely helps - thank you Luke [ @sum_giais ]

We don't need to worry about the server side, other than the box(es) it is running on as we are purely a networking team, but should we one day have to take that side on from a monitoring perspective then it's all good grist to the mill.

sum_giais · Answer

There's a few out there on Thwack. This is one that I've referenced in the past but there's one more (which I tried to find unsuccessfully). It was I believe a PDF but did duplicate a lot of what's noted in the link below.

Some areas I'd look into first to get a feel for where the environments at..

* Server architecture (OS version, patch levels.. they ARE getting patched right???)
* Environment Size (how many polling engines, web servers etc.)
* Orion Versions (latest and greatest or ancient?)
* Orion Modules Installed / Licenses Available (NPM, SAM etc..)
* Polling Engine resource consumption / polling rate
* Alerts enabled (focus on total)
* Retention policies in polling settings
* Custom Properties defined (looking at total)

Hope this helps!

thwack.solarwinds.com/.../orion-mvp-maintenance-procedures