ScienceLogic Reviews

I use the solution for IT infrastructure monitoring, specifically in complex IT environments with enterprise-grade level solutions. If I were a small to medium business, I probably wouldn't choose this provider. It is a heavily configurable, heavyweight, and scalable IT solution for IT infrastructure monitoring.

The solution excels in three areas: application monitoring, server monitoring, and network performance monitoring. Adding server monitoring into that list is quite key. 

One of its biggest features is its coverage of all the public clouds, which is significant because it is mostly an on-premise hybrid technology. If I have a complex hybrid infrastructure, it can look across all the major public clouds and virtualization solutions. 

It accommodates VMware, Hyper-V, KVM, and even older storage arrays and video conferencing and wireless technology. The real strength lies in its ability to operate across multiple landscapes, both modern and old, facilitating all of them. A major benefit is eliminating visibility gaps, which motivates me to consolidate tools. 

It offers over 500 integrations with a wide range of device types, referred to as PowerPacks, which are prebuilt integrations for hundreds, if not thousands, of integration types.

Our usual use case of ScienceLogic is as a strategic monitoring tool for all the customers in our company, and because of that reason, all the accounts and projects are migrated from other monitoring tools to ScienceLogic. Before migrating from other monitoring tools to ScienceLogic, first, we need to build the database servers as well as collector servers. Once the setup is ready, we then need to build the onboarding for the devices.

Before onboarding any device into ScienceLogic, we need to check the prerequisites, such as whether ping is open from the collector to the endpoint server, whether Telnet is working, and whether WMI is open. These are the basic prerequisites that need to be met before onboarding any device into ScienceLogic. Once the prerequisites are met, we then go for onboarding. Before we onboard, we first need to build the device groups and create the credentials we are using, either Windows or Linux.

Additionally, we need to prepare the templates based on whether it is a Windows server or a Linux server, reflecting the dynamic application which is essentially a small script that helps collect information from the endpoint server. For instance, if it is CPU, the script connects to the server to capture the CPU metrics. Similar dynamic applications exist for disk memory and others, based on customer requirements. Once the template is ready, I will push that template to the server, and that's the basic onboarding. After onboarding, when the OS classification is prepared, such as Windows 2021 or 2019, we need to validate data collection issues and enable the alerting rules and configurations. Alerts can be directed to ServiceNow tickets or email notifications, and based on that, we need to create the alerting rules.

The features and capabilities of ScienceLogic that I have found the most valuable include its ability to monitor server metrics as well as application-level metrics, similar to other infrastructure monitoring tools in the market. While each tool has its capabilities, ScienceLogic stands as one of the tools that monitor the server and application metrics effectively. However, it is not as capable for OS cloud platforms like Azure and AWS, and even for Azure, we need to build the collector with multiple processes involved. In comparison, other monitoring tools such as LogicMonitor are designed specifically for cloud-based monitoring. When it comes to infrastructure-level monitoring, tools such as SolarWinds, LogicMonitor, Nagios, and Zabbix are limited to scripting.

The integration of ScienceLogic with our existing IT ecosystems has significantly benefited our organization, as all alerts now directly go to IBM Netcool and then to the ITSM tool, ServiceNow. Initially, all alerts went through email notifications to specific users, but once integrated with ServiceNow, all alerts automatically create tickets through IBM Netcool, which then are assigned to the relevant teams based on SLAs and which ensures immediate response without missing deadlines. In the previous setup, there was always the chance an email could be missed, hence the integration with the ITSM tool has improved our alert management.

The primary use case is mostly centered around monitoring infrastructure and management.

The CMDB update and the automatic CMDB update are valuable, along with the new function of Skyler.AI, where I can use JNEI PeerSpot's assistance.

ScienceLogic is primarily a network monitoring tool. We used it alongside another tool. Initially, ScienceLogic was supposed to replace the old tool, but we used it for so long and never fully transitioned. ScienceLogic has a lot of benefits, with additional functionality through power packs and the ability to build things out manually. It is also more flexible than other tools but very manual to configure.

Initially, we received some help configuring ScienceLogic to monitor externally polling databases. ScienceLogic also combined that with its network device polling and gave us a complete picture. We had about 1500 branch locations and 100 on-premise network devices, so ScienceLogic was the tool that could merge those two worlds.

The best feature is the highly flexible graphs. If you have the time, the output allows you to input the precise information you want. In addition, the solution enabled us to make a single dashboard displaying about 12 vital statistics as we needed them.

It is also fairly extensible, and power packs are available. The modules slot in and extend the functionality. We had the most mileage out of monitoring UPSs, and power supplies in our data center.

We use the solution to monitor servers and DNSs.

The solution provides good infra-monitoring features. It sends me alerts.

We are using ScienceLogic for monitoring and orchestrating the remediation.

ScienceLogic has helped our company by monitoring. We have old tools we use and the functionality has been good.

We started off with infrastructure monitoring, then, over a period of time, we added on the application monitoring and cloud monitoring as well. It's been an incremental thing for us.

I like the collectors and I like the agent-less collector's functionality a lot. To me, that's been the top ones. I also like their integrations with the various types of devices that they've built out over a period of time. The power flow is great.