My ScienceLogic Review
Updated May 11, 2021
My ScienceLogic Review
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with ScienceLogic SL1
Multi-tended customer and internal managed service provider monitoring. Used across the company by technology owners and developers. Addresses inventory and network monitoring system servicing to CDW and its clients.
- Dynamic Applications: Able to build custom applications which makes us more scalable.
- CMDB population: Automatic CI population of assets and attributes provides excellent inventory reporting and helps with billing.
- Dashboards: Excellent ways to build custom views of devices and graphs helps to get a good view of the health of a customer's system.
- Upgrades: Looking forward to the new Yum deployment.
- Interface management: I want to be able to disable/not discover certain interfaces. Filters by type, device class, ifDescr, org, etc. would be lovely.
- Good impact: having a monitoring system that can be managed by anyone in our organization, not just a developer or NMS admin.
Yes - Nimbus
We were able to provide greater visibility to the client using the discovery applications and component build-outs.
Support of new devices occurs weekly if not more often. Recently we've been leveraging SiLo to populate attributes to provide automatic billing.
We are able to have a single pane of glass using ServiceNow. All monitoring events and CMDB population is managed by ServiceNow. SiLo is a great monitoring system that integrates well with ServiceNow using its integration server, which provides workflow and rules that work with our systems.
- We've found ways to discover managed services on client assets and populate attributes in the CMDB for reporting and billing.
- Reporting: we've been able to ETL data from Silo and provide reports to the client in ways that give the client a bigger picture of their environment and top items that need to be addressed.
iMonitor: device monitoring and collection configurations were managed via the CLI.
ScienceLogic SL1 Implementation
- Migrating from Nimbus to Silo
- Migrating from Sync Server to PowerFlow.
Using ScienceLogic SL1
250 - MSP monitoring, reporting, CMDB population, billing, troubleshooting.
30 - Networkers, Cloud, Servers, man there is many to list. Following scrum, there is a technology owner for each technology in our service catalog.
- Monitoring
- CMDB
- Troubleshooting
- Reporting
- Billing
- Automation
- Ticket enrichment
Evaluating ScienceLogic SL1 and Competitors
- Product Features
- Product Usability
- Product Reputation
The ability to create our own monitoring applications using python.
We compared with many different monitoring systems, it was a clear choice so I don't think I would change anything.
ScienceLogic SL1 Support
| Pros | Cons |
|---|---|
Kept well informed Immediate help available | Poor followup Problems left unsolved Escalation required Need to explain problems multiple times |
Yes, because we need the features and the expected SLA turn arounds.
Yes - Sometimes, sometimes not
On round 2 of attempting to migrate from Sync Server to PowerFlow, the engineer from PS was waaaaaay more better than the first. Knowledgeable and if he didn't know, he didn't guess, he escalated and figured it out. Strong work
Using ScienceLogic SL1
| Pros | Cons |
|---|---|
Like to use Well integrated Convenient | Requires technical support Lots to learn |
- Dynamic App building, if you'r just collecting basic stuff with SNMP apps
- The AP2 UI is getting pretty modern on most areas, keep that up
- Keeping all of the things via a powerpack is nice
- Programming the snippet apps, the copy code into a box, wait for config push
- sigerm troubleshooting
- Support