ScienceLogic SL1

ScienceLogic SL1 is used as the primary observability platform to monitor the health of infrastructure and applications in our Corporate Data Centers and Market locations. An integration using SL1 PowerFlow, with ServiceNow has allowed us to automate Incident escalation in a fine-tuned manner, ensuring events get escalated to the correct teams and individuals. This automation has allowed us to minimize NOC staffing requirements, essentially adopting a lights-out posture and only requiring staff to manage/maintain the product. As an early adopter of SL1, the product has played a vital role in our business for years, giving us the confidence we need in observability.

SL1 is used as a strategic monitoring tool for hybrid cloud environments, compute, middleware and database. More recently we have expanded into network device monitoring to provide a holistic monitoring platform for multiple user groups. We have a mix of hosted and SaaS platforms across all geographies. SL1 is deployed in an agentless mode which reduces the administrative overhead associated with legacy tools that were reliant on one or more agents to perform similar functions.

We use it for Infra monitoring. We have some pros and cons with this tool. Customer expectation is high! They need APM, AIOPS within SL when it is on On-prem.

SL1 is being used in our organization to manage and support the proactive monitoring of Datacenter devices and applications of the National Railway of Belgium. The scope of SL1 is quite wide as our customer's inventory is spread across 3 huge datacenters (2 on-premise and 1 public cloud). We monitor more than 3000+ servers, 2000+ databases, 200+ Network devices, and 300+ applications. In TCS, we have gone beyond the Out-of-Box monitoring and built our own custom DAs and RBAs to support our customers. The best feature about the tool is its auto-discovery mechanism which has helped us to build an advanced CMDB showing the relationship between hyper-v and VMware host and guest devices and also with underlying databases. A few business problems which we have across during implementations were 1. A very limited number of reports and that too very basic and do not comply with industry best practices (like Availability reports do not have a business and not business hour feature and even does not exclude the outages during scheduled maintenance). 2. Every small customization or help required from experts is treated as PS work and PS is very costly. 3. Sciencelogic Support engineers does not support and even does provide any suggestions on issues on customized DA even if the issue is because of the built-in ScienceLogic functions are a lot of internal Dynamic Apps (Like for filesystem, services, processes, availability, etc) where there is no visibility on the logic of how alerts are configured. 4. It is not possible to put only a few metrics (like DB services) in maintenance for a certain period. The entire server has to be put in maintenance mode and due to which even the OS-related alerts get suppressed.

I am an SME in HCL Technologies for the ScienceLogic SL1 monitoring tool and have five ScienceLogic SL1 customers in a shared environment. There was scope to manage the entire 60 customers from HCL Tech, but because the scope is limited and not advanced, many customers opted out for ScienceLogic SL1 as a tool.

Scope of use cases - each PowerPack should be tested properly for alerting. With the help of the application team, the DB alerts should be tested. They should consult with the DB team and ask what alerting is required and how relevant it is with the PowerPack that ScienceLogic SL1 offers, and accordingly, this should be enhanced.

Cognizant is an SI partner and Managed service provider worldwide. We recommend it to our customer for IT service Assurance. Cognizant is an SI partner and Managed service provider worldwide. We recommend it to our customer for IT service Assurance. Cognizant is an SI partner and Managed service provider worldwide. We recommend it to our customer for IT service Assurance.

SL1 we have leveraged for ITOPS, which includes IT infrastructure discovery, CMDB update, performance monitoring, fault monitoring, alert management, and auto incident creation into the ITSM platform. It helps to address ITOPS problems. A couple of use cases server operating system performance, database performance, network devices performance monitoring. Discovery of all IT devices and update the CMDB.

My organization uses ScienceLogic EM7 as our primary ticketing platform for our IaaS data centers. We also use ScienceLogic to monitor our events and also our managed services, such as servers, switches, and other network appliances. We also utilize ScienceLogic as our bandwidth billing platform, utilizing 95% billing rates on the greater of ingress and egress of network traffic.

We use EM7 and Integration server from Sciencelogic SL1 and applied it across 100+ customers across different sectors and would continue to expand the deployment with upcoming customers too.

We use it mainly to get monitoring data for our devices. It being used specifically in my department and the neighboring teams. We just use ScienceLogic API to get the respective details mentioned above.

It is an org level visibility.

We use ScienceLogic for monitoring our Managed Service customers, providing in-depth analysis on a range of hardware and software components in the data center. We also sell, deploy, and configure the application to any of our customers that require a monitoring solution for IT environments. Typically it is deployed across all departments.

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

ScienceLogic SL1 used [...] across [the] organization to manage the infrastructure environment to address monitoring issues, [and] perform automation against manual interventions to resolve issues, [and] ticket creations.

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

We use it to monitor our on prem and cloud platforms (Azure, AWS).
It escalates callouts to our engineers via PagerDuty and then raises a ticket in hornbill for the incident.

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

It is used for a particular product, called Unified Communications. ScienceLogic is monitoring and creating reports for this product.
In some cases, it is helping us to generate our report for our customers, i.e. when a customer migration happens.
Also, we create some intelligence about alarming, so the service is better monitored.

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

We're still in pilot phase to see if we can get the same efficiencies as other organisations have through their deployments.

Yes but we're still in early use cases.

We use ScienceLogic SL1 as our modes of monitoring of our devices within the company. We use multi vendor platform that are enrolled in SciLo. We use this platform to schedule maintenance window when we have activities, change, and other tasks. We also use it to monitor certificates and uptime of the devices.

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.

ScieLo is very useful, especially to us engineers, it makes our life easier and efficient as the automation from monitoring (networks and certificates validity) and integration to Snow ( ticket creation for any alert/error).

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

We've been using SL1 for some years for infrastructure and application capacity monitoring and we've been satisfied with the tool. The SaaS, agentless, open/customized tool brought us the opportunity to monitor our customer devices with power packs (some good, others not so much) and create our own monitoring collections, presentations, and monitors, which was good. The quick data warehouse and report/dashboard capabilities are a plus for the tool as well, for simple purposes they can fulfill what is required.

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.

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.

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

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 Science Logic SL1 as our monitoring and event-based automation tool to help manage our managed service customers networks and infrastructure. We also offer a Monitoring as a Service proposition, where our clients can just purchase a monitoring and automation service only.

ScienceLogic helps solve a number of problems:

1. Monitoring of status and performance of assets and services.
2. Displays and views via dashboards and Business Service views of the overall health/risk and performance of key higher-level services.
3. Event-based automation. ScienceLogic is a great platform to launch automated actions from. It comes with a large number of pre-build infrastructure specific scripts, which are easy to customize (with basic knowledge of Python).
4. Integration with other IT deliver tools such as ITSM tooling & CMDB.
5. Auto-generation of network maps that show asset dependency.

ScienceLogic is a great tool to bring together aspects of service operations and lead a customer from a reactive firefighting position towards a more mature operational model. The industry buzzword, AIOps, is a good one and ScienceLogic will start the journey to automating support and operations functions.

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.

We use ScienceLogic across the organization to monitor both our infrastructure and the health endpoints of services, and have found it gives us great visibility of system health. We are currently exploring moving away from competent level dashboarding and moving to dashboarding that will display the business services and show the impact a component failure has on that service as well as any other services dependent or linked to it.

In 2020 we carried out a migration to ScienceLogic’s SaaS platform to remove the requirement of both hosting and managing onsite DBs and this has also opened up new opportunities we are exploring within ScienceLogic.

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.

ScienceLogic brings significant abilities to the table (and on their roadmap) which enable critical business operations (such as maintaining our company website's 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.

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?)

We used it as the AIOps platform to do the proactive monitoring. In addition to that, we are also tied into our ServiceNow. It is used by the department and expanding to BU. The main focus of the ScienceLogic is to provide monitoring in a relationship, this gives the team the opportunity to quantify a lot of gaps that we had before.

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.

I have been using ScienceLogic for the past 2 years now and have seen significant improvement in the tool. It is a highly flexible tool and works efficiently for monitoring the entire IT infrastructure from hardware to software to cloud, application and synthetic monitoring. The tools has open snippet codes, which gives you the flexibility to adapt to any type of environment.

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.