Overall Satisfaction with ScienceLogic SL1
I use ScienceLogic SL1 at my job at Kyndryl to provide monitoring services of IT infrastructure for clients and customer support teams.
Both
- SL1 provides monitoring for various databases.
- SL1 can monitor all popular operating systems.
- SL1 uses monitoring agents and agentless monitoring.
- SL1 requires a lot of CPU resources.
- User Interface is not intuitive.
- Documentation is poorly organized.
- SL1 allows to support multiple clients in one platform.
- SL1 provides technology to support the shift to a hybrid workforce.
- SL1 allows to transform business with intelligent, data-driven automation.
ScienceLogic SL1 more cloud-oriented than Nagios. Product support is also very important for corporate users.
IBM Tivoli Monitoring is a relatively expensive solution that requires dedicated professional support and complex infrastructure.
Dynatrace is good for performance monitoring and analysis, but loses in price
Do you think ScienceLogic SL1 delivers good value for the price?
Not sure
Are you happy with ScienceLogic SL1's feature set?
Yes
Did ScienceLogic SL1 live up to sales and marketing promises?
Yes
Did implementation of ScienceLogic SL1 go as expected?
I wasn't involved with the implementation phase
Would you buy ScienceLogic SL1 again?
Yes
ScienceLogic SL1 Feature Ratings
Integrating ScienceLogic SL1
- Red Hat Ansible
- IBM Tivoli Netcool/Omnibus
- Servicenow
SL1 events are forwarded to Netcool which creates tickets in Servicenow. Software was developed for generating events and synchronizing the databases. Ansible playbooks was created to manage Sciencelogic reports and PP deployment
- Single Signon
- API (e.g. SOAP or REST)
- ETL tools
When integrating with ScienceLogic SL1, you need to carefully evaluate which system functions to integrate into external systems based on your needs.
Using ScienceLogic SL1
1500 - Customer support teams such as OS administrators, Application administrators and DBAs use Sciencelogic SL1 to monitor different customer resources for which they are responsible. The infrastructure support team also uses Sciencelogic to monitor company servers and network and generate usage reports. SL1 reports are also used in infrastructure development planning.
50 - ScienceLogic's SL1 support team include system architects, site
reliability engineers, technical support staff, program and delivery
managers, incident and change dispatchers and software engineers.
Sciencelogic support requires very good knowledge of infrastructure
components such as network and server hardware, virtualisation systems,
network protocols, operating systems knowledge, scripting skills and
experience with SQL
reliability engineers, technical support staff, program and delivery
managers, incident and change dispatchers and software engineers.
Sciencelogic support requires very good knowledge of infrastructure
components such as network and server hardware, virtualisation systems,
network protocols, operating systems knowledge, scripting skills and
experience with SQL
- Infrastructure monitoring
- Application monitoring
- Database monitoring
- Containers monitoring
- AIOPs integration
- Cloud monitoring
- Use Netcool event processing for SL1 alerts
- Resources DB synchronization between SL1 and LDS
- SL1 PP Reporting using Ansible command line
- SL1 device onboard & offboard using Ansible command line