ScienceLogic in the enterprise
October 29, 2019

ScienceLogic in the enterprise

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with ScienceLogic SL1

We are using ScienceLogic to tie events to our ticketing system. ScienceLogic allows us to set the priority of a specific issue that we then route to our ticketing system. If the priority is set high enough, we page the appropriate party to engage and work towards a resolution. If the issue resolves itself, the ticket will automatically close, but we still have a record of a potential issue that came up.
  • ScienceLogic is very granular in how items are monitored.
  • Powerpacks make it easy to monitor various systems with events predefined.
  • ScienceLogic is a very flexible platform.
  • The "legacy" interface is very confusing.
  • The granularity of the platform comes with a whirlwind of tinkering under the hood to make the system perform properly.
  • The very steep learning curve to get basic monitoring setup. However, once over this, the rest of the platform becomes easy to set up and maintain.
  • We have gained better visibility into troublesome hardware by having records of equipment going up and down.
Yes - We replaced some commercially bought, and some homegrown software. Previously, teams had their monitoring tool of choice whether it be bought, or created in house. With ScienceLogic, we moved these 1 off tools to an enterprise-grade solution.
We have gained much higher visibility into our hardware since the implementation of ScienceLogic. If a problem occurs, we can quickly jump into ScienceLogic to see what is alarming and gives a quicker reference of a place to start troubleshooting a problem. This, in turn, reduces the time needed to bring a system back online.
At this time, we are not using the product for growth of the department or business.
Currently, we are utilizing ScienceLogic in a ticket escalation fashion. Depending on the severity of the event generated in ScienceLogic determines the priority within our ticketing system. Depending on the priority within the ticketing system, this determines if an outage warrants paging an analyst. For instance, a server going down would be much different than a redundant PSU going offline.
  • At this time, we are only utilizing this platform for monitoring and alerting.
Basic server monitoring is an easy win for the platform. Powerpacks make it easy to monitor different platforms with events predefined and included. However, the system does not do well with near real-time polling. For instance, if you were monitoring uplinks on switches, you'd be best to poll at 5 minutes or more. The system would struggle if you try to monitor every minute.