ipMonitor -- A lackluster experience
Updated October 04, 2019
ipMonitor -- A lackluster experience
Score 7 out of 10
Vetted Review
Verified User
Overall Satisfaction with SolarWinds ipMonitor
We use ipMonitor in our platform and infrastructure teams almost exclusively, though other users are able to view the data when needed. We use the application to alert for unresponsive services, the F5 pool status, if a server can ping, and the various other ways that a system or server can fail and that make sense to monitor.
- A good place to look for an overall feel of how all systems are performing or if the alerts are configured correctly.
- Integrations with API services such as Pager Duty as well as SMS messaging.
- Somewhat clunky and painful to set up.
- Not very intuitive in terms of how to configure new alerts.
- Limitations on what can be monitored based on an agent-less configuration.
- Since ipMonitor is based on the number of alerts configured, it is hard to judge ROI. In general, I feel that the investment and yearly cost to keep ipMonitor in our environment does not justify the cost.
- It's very good at giving an up or down condition for specific servers or services, but not great on alerts that require a more granular configuration.
- Splunk Cloud and Nagios
I feel that ipMonitor does not provide the granularity or level of configuration we require for our teams. We actually are looking at other means of customizing our monitors using the products listed, which I think will provide my teams with the ability to create better alerts that can be customized easier and can provide more depth of monitoring and alerting.