Overall Satisfaction with ScienceLogic SL1
SL1 is being used in our organization to manage and support the proactive monitoring of Datacenter devices and applications of the National Railway of Belgium. The scope of SL1 is quite wide as our customer's inventory is spread across 3 huge datacenters (2 on-premise and 1 public cloud). We monitor more than 3000+ servers, 2000+ databases, 200+ Network devices, and 300+ applications. In TCS, we have gone beyond the Out-of-Box monitoring and built our own custom DAs and RBAs to support our customers. The best feature about the tool is its auto-discovery mechanism which has helped us to build an advanced CMDB showing the relationship between hyper-v and VMware host and guest devices and also with underlying databases. Also Sciencelogic has developed several powerpacks with third party tool like ELK, Kubernetes etc which are readily available for use. A few business problems which we have across during implementations were 1. A very limited number of reports and that too very basic and do not comply with industry best practices (like Availability reports do not have a business and not business hour feature and even does not exclude the outages during scheduled maintenance). 2. Every small customization or help required from experts is treated as PS work and PS is very costly. 3. Sciencelogic Support engineers does not support and even does provide any suggestions on issues on customized DA even if the issue is because of the built-in ScienceLogic functions are a lot of internal Dynamic Apps (Like for filesystem, services, processes, availability, etc) where there is no visibility on the logic of how alerts are configured. 4. It is not possible to put only a few metrics (like DB services) in maintenance for a certain period. The entire server has to be put in maintenance mode and due to which even the OS-related alerts get suppressed.
SaaS Only
- Auto-Discovery feature is very good which helps us in building relationships between hyper-v and VMware host and guest devices. Also, it helps in building the relationship with MSSQL Databases.
- Ability to perform bulk discovery and update in ScienceLogic.
- Flexibility to clone the Dynamic Applications and do custom modifications.
- Flexibility to create custom RBA's and do several automations.
- Also ScienceLogic has come up with several new power packs for integrating with third party tool like ELK, Kubernetes etc which are readily available for use
- OOB Reports (Availability and Capacity) are not very user-friendly and also do not fetch correct data most of the time or even show blank reports a lot of time. A very limited number of reports and that too very basic and do not comply with industry best practices (like Availability reports do not have a business and not business hour feature and even does not exclude the outages during scheduled maintenance)
- Dashboards do not have a lot of widgets and are hence are not able to create complex dashboards. There should be the flexibility of adding an additional column on dashboards through Custom attributes.
- Not possible to put only a few metrics (like DB services) in maintenance for a certain period. The entire server has to be put in maintenance mode and then even OS alerts get suppressed.
- The audit logs page does not get loaded and gives "504 Gateway Time-out" most of the time
- Every small customization is treated as PS work and PS is very costly.
- The SL1 support team does not support and even does provide suggestions on issues on customized DA even if the issue is because of the built-in ScienceLogic functions. There are a lot of internal Dynamic Apps (Like for filesystem, services, processes, availability, etc) where there is no visibility on the logic of how alerts are configured.
Do you think ScienceLogic SL1 delivers good value for the price?
Yes
Are you happy with ScienceLogic SL1's feature set?
Yes
Did ScienceLogic SL1 live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of ScienceLogic SL1 go as expected?
Yes
Would you buy ScienceLogic SL1 again?
Yes
- Has integrated ScienceLogic with various inhouse tools of customers through Inbound traps, emails, and API feature and hence event correlation could be built
- Have been able to integrate SL1 with ServiceNow CMDB to automate CI population and Build a relationship of CI with INcident, Change modules.
- Microsoft System Center Operations Manager (SCOM), Zabbix, IBM Tivoli Monitoring, HP BTO (formerly OpenView) Discontinued, Broadcom Unified Infrastructure Management and formerly from CA
SL1 was selected by our solution architects and I was not involved during the selection process. But during implementation and configuration, I realized that the tool is easy to use because of its discovery feature. Also, it is flexible in use and we are able to create our own DA and RBAs
Integrating ScienceLogic SL1
- ServiceNow
- Azure
- Solarwinds
OOB pack for integration did not suffice the requirement and hence we need to get help from PS to build custom integration for our stack.
- SAP Solman
- ELK
- Graffana
- Kubernetes
Yes, i could see several powerpacks for integration whcich I will use
- Single Signon
- API (e.g. SOAP or REST)
Please help us with documentation of how we can enhance the integration by providing the details on powerpack on how its developed.
It is difficult to approach to PS each time we need help on some development in the PP
It is difficult to approach to PS each time we need help on some development in the PP
ScienceLogic SL1 Support
Pros | Cons |
---|---|
Good followup Knowledgeable team Problems get solved Kept well informed Immediate help available Support cares about my success | Escalation required Need to explain problems multiple times |
Yes - No, several bugs are left to be addressed in future releases and resolution was very late. Several bugs have reoccurred which were fixed in earlier versions
Yes, we have come across with several instances when during weekend, there were issues observed on the stack. We have immediately raised P1 with SL and although with thin support present during weekends, we were able to resolve the issues in a timely manner.