Trials and tribulations of SciLo as part of a managed hosting service provider.
April 25, 2019

Trials and tribulations of SciLo as part of a managed hosting service provider.

Kelly Price | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with ScienceLogic

We use it across our entire organization to monitor customer systems. We're a managed hosting and colocation provider with 16 datacenters across the USA. If a system goes down, we're the first responders to react to the issues. Thus, any infrastructure we build for a customer that we onboard is tracked, monitored down to the application level, and acted upon. We also present the metrics out to our customers.
  • SNMP data gathering.
  • API/Program data gathering
  • Statistics and presentations.
  • Platform stability.
  • Documentation, especially SciLo API documentation, when integrating into ScienceLogic.
  • Diagnostic information is readily available.
  • Positive: Enabled our support teams to jump on issues quickly.
  • Positive: Enabled easier views on metrics for our customers.
  • Negative: Administrative hassles tend to fly in Support's face, causing false positives.
  • Negative: Lack of developer documentation (SciLo API) leads to longer R&D cycles for integration with third-party products.
We are able to drill down to whatever level we need, from regular hardware down to applications and interfaces. This is further helped by the use of dynamic applications we write to support customer monitoring.
We integrate from our CRM system, Epicor ITSM (which itself is highly customized), to control which systems are monitored and when. Systems are discovered, with certain types of monitoring applied via templates, controlled by Epicor ITSM. If a system is decommissioned, it is auto-removed in SciLo by our integration. This integration, however, has its own technical debt, which can be solved with better API documentation from SciLo.
ScienceLogic allows for agent-less monitoring of systems, unlike others that require an agent to be installed on systems. While SciLo does have an agent, it is an optional feature that is useful for a small part of our hosting and management offerings. AWS monitoring definitely will benefit from using the SciLo Agent, but (once again) it's a small part. Most of our systems are monitored over SNMP.
It is good at monitoring, data gathering, and topology mapping of your equipment. However, it has issues where the movement of equipment is a concern. For instance, if a virtual machine in a VMWare "development" or "pre-production" cluster or host is built, and you want to retain the performance data that you gathered through it's VMWare integration and SNMP statistic gathering, it will (as of this year) drop and recreate devices should you move the device across host/cluster/resource pool boundaries. Only recently is it being fixed.