ScienceLogic for the win.
April 25, 2019
ScienceLogic for the win.
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with ScienceLogic
We are an MSP that uses ScienceLogic primarily as an event notification and performance monitoring tool for multiple customers. Lots of customers have many different types of technologies implemented, so updated power packs are very beneficial to us. We take event notifications and sync those to ServiceNow for incident creation. We have a few devops type runbooks that take data and take some sort of action based on that but are looking to add more in the future.
- Automation: the runbooks are very powerful and have multiple use cases, can take almost any custom action for a number of different reasons.
- Device management: with multiple environments and types of devices, the ability to dynamically discover and build relationships with components is key.
- Event management: customizing event policies is also critical for us, as not every customer has the same idea of critical, major, or minor.
- Update process: Our updates have been infrequent due to the fact that we risk outages or lost data every time we upgrade. We would like more logging, the ability to update nodes independently.
- Predictive Analytics: We would like to get ahead of the problems before they happen.
- Fine tuning: Adding customization options pretty much anywhere they can be implemented would help us greatly.
- Event and incident management is one of our key services as an MSP, so without the platform, we would be relying on manually checking on different systems' health and performance, which is not even a feasible option.
- The ability to automate different actions and respond to events dynamically has added some value currently, but will most likely increase in the near future.
- Some of the negatives: as tickets are created from other teams, they commonly question the accuracy of events. As we understand that some of that is due to the underlying technologies like SNMP. Accuracy checking due to mistrust has created some loss of value.
ScienceLogic was at the company before me, so I was not there to see the change, but I can tell you that our internal systems are monitored very closely and adding visibility into those has increased our effectiveness as a whole, limiting downtime and incident responses.
As we acquire new customers or move current ones to new technologies, the ability to have power packs released that already support monitoring of them only increases our company's effectiveness as a whole. For instance, AWS technologies, which seemingly change daily, can still be accurately monitored and discovered with multiple components of each service.
Right now, the main runbook that we have us updating ServiceNow and creating tickets. We have not yet purchased ServiceNow integration. We also are currently working on projects that will include runbooks that will reach out to APIs and restart certain devices, as well as pull data from those. Projects like this coming down the pipeline will very deeply involve runbook automation.
- ServiceNow ticket creation and updating: we have had to build this custom as we do not have the ServiceNow integration.
- Device Reboots: we take steps to resolve tickets after events come in by attempting to reboot or restart services. Some with built-in power packs and actions, others with custom built python snippets.
- Data analysis: we are pulling multiple data points from the internal API and enriching it to provide to teams' problem tickets.
ScienceLogic has already incorporated the majority, if not all of the features that we would need multiple tools to replace. The platforms' ability to pull information from other third parties and make the data useful makes it even more useful than other specified tools.