Sometimes its difficult to persuade an organisation to allow you to get your monitoring tentacles deep into their environment. It feels like an uphill battle.
I've had many internal meetings recently, where my colleagues quiz me about the dangers of letting Solarwinds inspect the network using SNMP / WMI.
Supportability by Microsoft of consistent reads against SQL databases with Solarwinds, seem to be a concern.
I try my best to reassure them and point out the benefits and resources that will be provided as a result of letting me monitor their environments.
Once you raise changes to open your network up to allow Solarwinds to monitor nodes and get Netflow up and running and start to monitor apps in SAM, people start to ask you questions about what they can achieve with Solarwinds and realise that actually, SolarWinds is quite useful.
It always seems like such a challenge to get monitoring in place but its always worth it in my experience.
I wish that network atlas was a little fancier and combined with network topology mapper, more bells and whistles please.
I'd like to see IPAM combined with NPM. I never understand why that is a separate product.
I've used a lot of monitoring packages over the years and Solarwinds is definitely a good choice for me and the organisations I work with in the UK.
Has anyone else had any experience of having to sell monitoring to the companies they work for, while setting it up at the same time? What are your experiences and how did you best sell the benefits of Solarwinds?
