ScienceLogic SL1 review and why you should use it
Overall Satisfaction with ScienceLogic SL1
We use Science Logic SL1 as our monitoring and event-based automation tool to help manage our managed service customers networks and infrastructure. We also offer a Monitoring as a Service proposition, where our clients can just purchase a monitoring and automation service only.
ScienceLogic helps solve a number of problems:
ScienceLogic helps solve a number of problems:
- Monitoring of status and performance of assets and services.
- Displays and views via dashboards and Business Service views of the overall health/risk and performance of key higher-level services.
- Event-based automation. ScienceLogic is a great platform to launch automated actions from. It comes with a large number of pre-build infrastructure specific scripts, which are easy to customize (with basic knowledge of Python).
- Integration with other IT deliver tools such as ITSM tooling & CMDB.
- Auto-generation of network maps that show asset dependency.
Pros
- Status and performance monitoring with great de-duplication of events.
- Event-based automation.
- Easy integration with ITSM tools for CMDB, Incident Management and Change Enablement.
- Dashboards and Business Service views.
- Network dependency mapping.
Cons
- One of the strengths of ScienceLogic is its investment in the roadmap and development.
- SL always listen to ideas on how we think we can improve the product.
- SL1 has simplified our event monitoring system, taking less time to manage than competitor products.
- SL1 is starting to save engineering time by reducing the effort and time taken to get the information required during the Incident process, reducing the Mean Time to Repair (MTTR).
- SL1 saves time as its discovered asset information can be auto update the CMDB.
- SL1's deep monitoring catches more events before they turn into Incidents enabling a more proactive approach.
Yes - ScienceLogic replaced a mish-match of SolarWinds instances.
SL1 has much-improved visibility of and our ability to manage our customer environments.
This has improved as SL1 offers deeper levels of monitoring and also easier management of the platform (Ease of management is important as changes are more likely to get done. If I make an improvement to a monitoring method, I can easily apply that update to all of those monitored devices across multiple customers).
The Business Service views mean that I can easily create views into the monitoring data that are applicable to different levels within an organization. For example, an overview of business services for director level and a lower level performance view of assets for engineer level of employee.
This has improved as SL1 offers deeper levels of monitoring and also easier management of the platform (Ease of management is important as changes are more likely to get done. If I make an improvement to a monitoring method, I can easily apply that update to all of those monitored devices across multiple customers).
The Business Service views mean that I can easily create views into the monitoring data that are applicable to different levels within an organization. For example, an overview of business services for director level and a lower level performance view of assets for engineer level of employee.
We are using ScienceLogic SL1 to support our Service Portfolio of managed services (Enterprise networks, Collaboration, Datacentre & Cloud and Security). We have reached a level of expertise where we are also able to offer a ScienceLogic service as well (Monitoring as a Service).
The ability that ScienceLogic provides us enables us to provide more value to our customers by understanding and providing them with a view into the services they run across the infrastructure we support for them. We are seeing that customers, having seen what we do for one service have asked us to provide monitoring for other areas that we don't provide managed services for, so that they have greater visibility across the whole estate.
The ability that ScienceLogic provides us enables us to provide more value to our customers by understanding and providing them with a view into the services they run across the infrastructure we support for them. We are seeing that customers, having seen what we do for one service have asked us to provide monitoring for other areas that we don't provide managed services for, so that they have greater visibility across the whole estate.
This is SL1's key strength. SL1 has a great API that enables us to take the data from SL1 and share it with other systems.
- Integration with ITSM case management tool for Incident Management.
- Integration with CMDB asset management database - auto-update the CI's within the CMDB
- The CMDB also includes the dependency mapping that SL1 discovers and updates - this information is key to Change Enablement and RFC (its easier to highlight what's affected by changing a specific CI)
- Event-based automations gather additional information that updates the ITSM tools case, saving engineering effort and leading to reduced MTTR.
- In specific circumstances we can fix the issue using automation, leading us towards 'No Ops'.
- SL1 is a springboard on the route to AIOps / the automation of services.
- We have developed an innovative vulnerability management system using the SL1 provided asset data.
- Tighter integration with ITSM tool than expected.
SL1 is my monitoring and performance tool of choice.
It has greater functionality, flexibility, scaling, and easier management than the competition (For example Logic Monitor, SolarWinds, Broadcom UIM, Kaseya).
Cisilion selected SL1 because of its flexibility, wide coverage, and ability to bring everything together (removing silos).
It has greater functionality, flexibility, scaling, and easier management than the competition (For example Logic Monitor, SolarWinds, Broadcom UIM, Kaseya).
Cisilion selected SL1 because of its flexibility, wide coverage, and ability to bring everything together (removing silos).
Comments
Please log in to join the conversation