ScienceLogic SL1 Reviews

We are an MSP providing monitoring and analytics services to audio/video and UC customers. We use SL1 to monitor customers' audio / video integrated rooms and UC endpoint-enabled rooms including Poly, Cisco and LifeSize devices. We have a 24/7 customer support operation centered around receiving customer device events from SL1, auto-generating tickets into our ITSM platform and providing real-time analytics and trending report analysis through SL1 collected data. This data and analytics help customers make business decision surrounding the use and optimal deployment of their conferencing and enriched media services to their internal teams.

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.

ScienceLogic brings significant abilities to the table (and on their roadmap) which enable critical business operations (such as maintaining cisco.com health and availability) to track against our ServiceNow (CMDB) data and our ScienceLogic (IT Infrastructure Monitoring) deployment. We have replaced our legacy / homegrown system with ScienceLogic to enable our on-prem, private cloud and multi-cloud deployments (sometimes using all three) the ability to ensure health and availability.

We are looking to move to ScienceLogic's AIOps and data lakes to further simplify the transformation of our event-storms to meaningful business information.

As Cisco IT, 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 Cisco 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 Cisco IT currently renders Host Clusters, Application Clusters and Application endpoints (regardless of lifecycle).

Cisco IT will be working with ScienceLogic on the 8.12 view of Application Management (which as configured won't match the Cisco IT 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 Cisco IT will interact with Business Services since Cisco IT Management wants Application Monitoring, but Cisco IT 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?)

We are using ScienceLogic SL1 in a multi-tenant environment with our central database in the AWS Gov Cloud. The benefits of the ScienceLogic SL1 platform for us and our customers is the ability to provide access to our customers and their technical staff to use beyond just a monitoring solution but as an operations management platform as well providing insights into the operating environment.

Yes. The ability to bring in multiple components of the IT or business service provides a holistic view of what's actually happening. Based on that, we can quickly get to the root of many problems that may be occurring in the environment. We are now beginning to look at the components of applications that can include Server/OS, Network, processes running, and other points of collection. That is a powerful aspect of the platform that will be extremely beneficial going forward.

ScienceLogic SL1 is being used as a monitoring tool for our managed services and managed hosting customers. It's being used mainly to monitor things such as network equipment, servers, and storage. We have a team of engineers that help to manage ScienceLogic SL1 but it's used across multiple departments in our organization. Our NOC engineers and account managers have varying levels of access to the tool depending on their job function. We have the alerting feature of ScienceLogic SL1 integrated into ServiceNow, which we use for our CMDB and ticketing purposes.

Our NOC now has much better visibility into the critical issues across our organization. We work hand in hand with the NOC to ensure only the important event bubble up to the top and show up on the wall. ScienceLogic SL1 does a fairly good job of allowing customized suppressions of events deemed unimportant by the NOC or one of our customers.

SL1 is used by the whole organization. It's used to monitor both internal devices like core network devices, servers, and customer devices such as virtual firewalls. Performance and availability are measured regularly and reduce outages due to the alerts that are being created before any outage.

My organization is using ScienceLogic as an aIops monitoring platform for our customers. Currently, it's being used by a department. It is addressing the problem of a management and monitoring solution for customer's requirements, with actionable insights to resolve the problems.

Currently, we are using one tool for event monitoring, another one for event management, and yet another one as an ITSM solution. We need to integrate them. ScienceLogic is an all-in-one solution when added to an AI/ML-driven solution.

ScienceLogic SL1 is being used across the entire organization. Throughout our implementation we were able to work with both Professional Services as well as support to work through some minor issues. I have always felt that working with our vendors as a partner is more beneficial for all parties. We are able to get access to more enginering resources which in turn help to move the product into a more beneficial direction for both us as a customer as well as a product for ScienceLogic.

With other monitoring products, it has to be used with a client to view the current status of the infrastructure and not everyone could use it. With ScienceLogic SL1 everybody can access our monitoring portal via browser and customize all the needed views, reports and dashboards to their specific needs.

Whole Org. We use it to monitor our keys systems and our customer's systems. Providing performance data and event data.

We are in the process of deployment of business services. However, I am excited to see how this will change the way we view monitoring and SLAs.

Multiple deployments of ScienceLogic SL1 within Telstra are used to monitor many thousands of internal and customer based devices and services and alert different assurance and support teams of issues.

We have been able to build many business service definitions to represent multiple infrastructure and application elements and represent these to stakeholders.

ScienceLogic SL1 is being used as the enterprise monitoring, reporting, and alerting tool for several of our customers. It is integrated with Service Now for incident and CMDB synchronization to quickly automate scheduled outages, full systems life cycle including commissioning and decommissioning automation, and helpdesk integration. It is also used to monitor Cloud resources, and tie back into the billing system via its API capabilities.

If implemented holistically, e.g. if it has an IP it's in SL1. The tool provides unprecedented visibility into every level of the OSI Model. The true challenge becomes working with SMEs for each device or application to determine what KPI they want to monitor and alert on.

As a provider of managed services SL1 is our preferred choice and has been our centralized monitoring platform for several years. We adopted SL1 both for our own Datacenters and for our Customers when delivering managed services, cloud, data center, storage, network.

I believe visibility and transparency have improved considerably. Also and more importantly than the question perhaps seems to indicate: SL1 has been a great platform for actually improving monitoring capabilities, say from two dimensional dead or alive monitoring towards scenario/service based monitoring thus improving quality of managed services and business continuity and laying the ground for DevOps and CSI work.

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.

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.

We are currently using SL1 for the Managed Service business.

ScienceLogic SL1 not only provides visibility internally but also helps customers understand what their environment looks like today and helps them evaluate for future demands/requirements that the business will need--to start thinking in a proactive way rather than reactive.

Currently, we are using ScienceLogic for one of our accounts as it is a rich platform and it connects so many technologies.

NA

We use ScienceLogic SL1 to monitor devices nationwide and to alert on outages. In addition, we monitor the server health to determine if additional resources are needed and if failure has occurred.

Access to devices across the nation

We are using ScienceLogic SL1 to monitor our whole network infrastructure across the world. It is used by multiple departments so that we have a single monitoring solution.

It has not changed.

We use ScienceLogic across our organization for monitoring and asset management. As an MSP, ScienceLogic gives us the insight needed to ensure a quick response to issues arising on critical infrastructure that would affect us internally as well as our customers.

ScienceLogic has given us very detailed visibility across our infrastructure.

We are using ScienceLogic SL1 for our managed services business. It is used to manage and monitor all internal infrastructure as well. As of yet, we haven't addressed any milestones from our previous monitoring tool. COGS are a first-hand business problem that it has addressed.

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.

Used to monitor servers, network, and application. It is mainly used by IT only. Application monitoring proved to be difficult, so most of that has been written in-house or leverages other monitoring tools and events are sent to ScienceLogic.

No change/No improvement

We are deploying the SL1 for our customers. This product is typically used by organizations driven by the DevOps model. IT allows them to harness the elements of AI into the infrastructure monitoring and IT Service Management. Surprsiningly, it also has a simple ticketing system built-in. However, in most cases, the customers decide to integrate with their existing ticketing systems. While I have seen IT using it, the business hardly ever gets more than a dashboard to see which services are up.

In the case I have described, it was not exactly the change invisibility. It was a unification. Instead of having two separate products, the customer ended up with one holistic view of the entire infra (network, server, and application levels). Because literally anyone with an AD account was able to log into the system, the administration was simple and straight forward.

SL1 is being used for a Fortune 500 client as a means for network and server monitoring. It is being used by a particular BU at the client and is not rolled out throughout the whole organization. SL1 addresses our needs for network monitoring and alerting to the NOC for resolution.

Our level of visibility with the use of SL1 has remained constant. With SL1 we have been able to increase the number of alerts and events and allowed our organization to become more proactive instead of reactive. When we are able to fully integrate AIOps we will become an automated solution for any network issues.

I use ScienceLogic SL1 to perform infrastructure monitoring for my customer. It addresses the following business problems: (1) We use separated monitoring tool in server & network environment before and use different method to monitor. We choose to monitor server & network devices in one tool. (2) Auto-scanning for inventory is what we like to use.

We used a traditional monitoring tool like Nagios before. After using ScienceLogic SL1,
(1) the agentless function is different from the traditional one and supports rapid deployment with the standard platform.
(2) Event handling function is different from traditional tool and can prevent duplicate alert and prevent mass tickets (after integrating with ITSM tool for auto-ticketing)

This would be best answered by our customers, but I do honestly believe that they have managed to gain valuable insights into their estate through proper implementation of the SL1 product.

Currently, it's employed in our managed services practice across a couple hundred clients. We utilize ScienceLogic SL1 for alerting in break fix scenarios as well as health reporting in multiple technological disciplines.

It has forced a re-adoption and fresh approach to the monitoring mentality that has been set in stone for a while. We're using this opportunity to bolster and improve what we should alert upon as well as tune out what we shouldn't--this has had both a positive and negative impact but moreso the former as customers are getting reports they previously did not have.

SL1 is our recommended strategic tool for monitoring. It must be used for all new customers. Its aim is to monitor servers, hardware and to be integrated in a global solution, that is event management, ticketing tools by example. Different strategy could be used to deploy the solution: On-premise, on SL1 cloud or on our cloud.

SL1 is not yet deployed in our customer infrastructure, so it is difficult to have a clear view. Nevertheless we hope that SL1 monitoring could offer more functionalities for all kind of monitoring such as Docker and Kubernetes. We hope also that SL1 could cover all specific monitoring already used by our client.