ScienceLogic SL1 Reviews

Yes. Automating [the] discovery of granular details within the environment brings more details/awareness on the environment.

We can easily monitor devices and alerts us users if we need to take actions. We can also use this to schedule maintenance windows so it will not alarm or notify other Engineers that a specific device is down. It made monitoring devices easy by use of scripts and automation.

So far NO, not yet experienced to modify my level in ScienceLogic SL1.

ScienceLogic SL1 allows for better monitoring and visibility to the entire enterprise. Honestly, nothing is more visible than it was before however it is easier to be aware of the bigger picture and harder to miss critical problems. This platform will allow for more work to be done by each NOC tech if less time is spent on looking at numerous different monitors.

We were able to provide greater visibility to the client using the discovery applications and component build-outs.

Yes but we're still in early use cases.

NA

Yes, absolutely. ScienceLogic has good features for discovering items in any environment.

The capability of ScienceLogic to deliver out-of-the-box reports and dashboards (according to the maturity of the required/technology powerpack) changed the visibility across the infra, application, and services overall. Now, the customer and service provider, have, without the necessity of spending time developing easy and quick reports and dashboards.

ScienceLogic was implemented before I started 4 years ago, I don't know what they had before that.

In one screen we can see if there is any issue in the service.

SL1 has much-improved visibility of and our ability to manage our customer environments.
This has improved as SL1 offers deeper levels of monitoring and also easier management of the platform (Ease of management is important as changes are more likely to get done. If I make an improvement to a monitoring method, I can easily apply that update to all of those monitored devices across multiple customers).
The Business Service views mean that I can easily create views into the monitoring data that are applicable to different levels within an organization. For example, an overview of business services for director level and a lower level performance view of assets for engineer level of employee.

When moving to ScienceLogic we gained a deeper insight into our infrastructure, its functionality and health alongside providing us with a more in-depth dashboarding tool-set.

We are also hoping with the move to service orientated dashboarding this will provide us with better visibility of service functionality, the impact a service issue has on other services, and also allow us to provide the business with dashboards to be able to view their service health.

Being a Managed Service Provider, we have greatly increased our visibility into customer networks and devices using SL1. It provides a solution that allows us to not only be alerted to customer events and issues, but through the single pain of glass design and multi-tenancy of the application, we can safely and securely offer customers visibility to the dashboard to see their events and our team responses as well.

Not yet. This is too early for us to look into this particular topic. ScienceLogic SL1 was deployed in Dec 2019. Currently, we are going through a lot of fixes and functionality that we need to incorporate/enable/change so we adhere to SLAs.

We see it has significant value to the question here, however, we have not had time to quantify and evaluate.

We forced a common view to be rendered in ScienceLogic so that the vast majority of our 2200 users could see where they were supposed to go based on droplets of our IT culture which we sprinkled across the ScienceLogic legacy user interface. 80% of our customers will use ScienceLogic without really using ScienceLogic. 20% of our customers will deeply use ScienceLogic PowerPacks, etc. Everything has changed, but our core structure is visible throughout. If anything, the new structure is now more inline with our recently updated CMDB (ServiceNow) structure as opposed to our legacy CMDB (EMAN) structure. (These have been multi-year change cycles.) ScienceLogic IT Services are how our IT culture currently renders Host Clusters, Application Clusters and Application endpoints (regardless of lifecycle). We will be working with ScienceLogic on the 8.12 view of Application Management (which as configured won't match our model or requirements). We expect sometime in the 8.13 or 8.15 release cycle that we may have something usable which we will move our Application Monitoring and Service health monitoring onto Business Services and Application Health. For now, we will continue to use IT Services though Host Clusters will slide down into Device Services. It is unclear if we will move Application Clusters will move up to Business Services. We need more discussions to determine how we will interact with Business Services since our IT Management wants Application Monitoring, but we can't consume it because our view of an application isn't supported by ScienceLogic's definition that it is rooted by a process in memory on a given box. (We run many applications through the same nginx / apache process... Exactly which application is up and which is down?)

Yes it has definitely changed the level of visibility, now it gives us more insight into the network performance. Interface error and discards across the interfaces help us to troubleshoot the latency issue of the applications. Bandwidth utilization of the device helps us to decide if it's the best time to increase the number of links, thus helping in maintaining the smooth performance of the applications.

Yes we have changed due to a unified view of the data. This is now the big data for us. We are still under deployment at this moment as we are very new in the game within Canada. At this point, I cannot tell you if that is the case, but we do see some progress on it already.

With ScienceLogic we have the ability to scale visibility to our needs. It allows for help desk operations to get a quick and easy look into infrastructure and applications that they do not have other access to in order to more quickly address issues. Sometimes the ability to show something that looks correct can quickly determine who can notice if something does not look correct.

ScienceLogic has allowed us to have a holistic view of our entire infrastructure. We definitely have an hybrid infrastructures, comprising internal data centers, private clouds and public cloud service. We have increased the number of devices, companies since we started using ScienceLogic. ScienceLogic has provided provide us with more flexibility and the potential for carving out the perfect environment for a company’s multifarious needs.

It is an org level visibility.

Still too early to tell, in the next months we will have a better understanding on this topic.

i am working as tools consultant with more than 8 years of experience in the industry and has worked on many infra monitoring tools such as UIM, spectrum, solarwinds and now sciencelogic as well. starting with support to teh implementation teams, i am now being part of COE team wherein we provide recommendations to our new customers.

Yes, our level of visibility improved with ScienceLogic by delivering in-depth visibility with a high affinity by the technology specifics.

There was a slight visibility as the ScienceLogic GUI presents dashboards and reports that can be used accross the customer hierarchy. Giving that we have management and technical teams accessing and using the tool. Although it is not the goal of the tool, we can see a slightly usage for capacity management as well. Given that, although not being specialist in some areas (as dashboards, reports, capacity) the tool is also being used in those areas.