Item: ScienceLogic SL1
Rating: 9
Author: silvia morini

Overall Satisfaction with ScienceLogic SL1

Use Cases and Deployment Scope

SL is being used as the monitoring tool for some of the accounts we support. We are exchanging Tivoli tool to SL tool for device monitoring.

Pros and Cons

Pros

Helpful dashboards.
Agent-less - easy to implement.
Easy to add collectors or increase the number of device monitored.
Good support.

Cons

Customization on monitoring needs.
Facilitate the credentials process.

Return on Investment

we just completed the SL implementation, but DPE is very pleased and willing to use the tool.
It is more adaptive for customer's needs.

Products Replaced

Yes - we replaced ITM (IBM TIVOLI) to SL

Impact on Infrastructure Visibility

I was the project manager running the deployment of the tool across one of our accounts, so I received the feedback from supporting teams, and even though they are still in the learning curve, they are happy with results and willing to take advantage of the tool.

Using ScienceLogic to Support New Business

IBM is working to use SL as the new focus tool for device monitoring.

ScienceLogic Integration

We integrated SL with our ticketing tool - Netcool. It is running very well.

Innovative Uses

It was able to replace ITM in all needs.
We are already planning new features - working on some cases with SL supporting team.

Alternatives Considered

Account manager chose SL because of the capabilities it has over cloud environment.

Likelihood to Recommend

It is very good for cloud environment and very adaptable to customer's needs.

Comments

Please log in to join the conversation

Chris Boswell
commented 6 years ago
Thanks for the review Silvia! IBM has selected ScienceLogic as their preferred solution for monitoring and event management for hybrid and multicloud workloads as part of their broader MultiCloud Management Services (MCMS). Customers adopting cloud are seizing the opportunity to consolidate tools and ITM is one of a number of solutions that are being targeted for migration. Note on the "con" comment regarding credentials. ITM is an agent based solution, so anyone moving from agent-based to agentless approach will tell you there is some prep-work associated with gathering credentials with the right authorization levels to instrument devices. Because we support so many device types and employ a variety of protocols for discovery (including PowerShell, SSH, API's, SNMP, etc.) gathering the right credentials is an important first step in preparing for a successful deployment.

Feedback from SL migration over ITM