Best Practices for New Users

Hopefully this is the right place for this questions.   I am looking for the best practices for setting up our new SolarWinds system.  I have approx. 350 sites with about 6000 network devices, supported at this time be 3 different regions.  How should we lay this all out.   Our old system is a major pile and we want to set SolarWinds up correctly from the beginning. 

Parents
  • It's a good challenge to set up a monitoring platform for an environment of that size.  Make sure you review the architecture and scalability docs and don't try to skimp out on your database server, that's by far the most important part of the infra.

    Once you get your system installed I think the first order of business is figuring out your custom properties.  Don't be fooled, there is no way to manage Orion at scale without using them. 

    I always deal with requests by assuming nothing is ever a one-off, if I do something for one case I'm going to need to figure out a way to make that flexible enough to handle many cases.  Just as an example sometimes people create a bunch of true/false properties when it would be more practical to have a single property with a drop down pick list.

    As you get comfortable with your environment and pin down all the custom properties you'll eventually get sick of doing things by hand in the GUI the slow way.  By that point you are going to want to get familiar with SQL and SWQL and the Orion API.  You'll end up saving yourself huge amounts of time and make it a lot easier to enforce standards and make sure things aren't broken or slipping between the cracks.

Reply
  • It's a good challenge to set up a monitoring platform for an environment of that size.  Make sure you review the architecture and scalability docs and don't try to skimp out on your database server, that's by far the most important part of the infra.

    Once you get your system installed I think the first order of business is figuring out your custom properties.  Don't be fooled, there is no way to manage Orion at scale without using them. 

    I always deal with requests by assuming nothing is ever a one-off, if I do something for one case I'm going to need to figure out a way to make that flexible enough to handle many cases.  Just as an example sometimes people create a bunch of true/false properties when it would be more practical to have a single property with a drop down pick list.

    As you get comfortable with your environment and pin down all the custom properties you'll eventually get sick of doing things by hand in the GUI the slow way.  By that point you are going to want to get familiar with SQL and SWQL and the Orion API.  You'll end up saving yourself huge amounts of time and make it a lot easier to enforce standards and make sure things aren't broken or slipping between the cracks.

Children
No Data