I am a long-time (since 2008) SolarWinds user, who has recently started in a role at a new employer assisting with a migration to the SolarWinds Orion platform (NPM/SAM at first, others to follow). The software is already installed, and I've been brought in to assist the migration.
Along the way, I think we've all learned things along the way that we wish we had known when we first got started, and I'd like to hear some of yours. I'll add a couple of my own.
- Create an alert that triggers if a device is up and one or more of its interfaces are in an unknown status. This could indicate that hardware was changed and needs to be updated in NPM.
- Create an alert that triggers if a volume is not responding to polls. This could indicate a drive was swapped out and the node resources need to be updated in NPM.
- if you have additional polling engines, monitor them (including the Orion services) from the primary Orion server, even if you don't monitor anything else from there.
- Monitor the primary Orion server (including the Orion services) from a secondary poller and/or externally.
Mostly, I want to help them learn from my past mistakes/bumps in the road. What suggestions would you give if you were in my position?
Thanks,
~Terry