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 primary use case of ScienceLogic ( /products/sciencelogic-reviews ) for me is hybrid monitoring. This involves monitoring cloud infrastructure, data centers, or hyper-converged environments like Nutanix, as well as hardware monitors.
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 is a hybrid monitoring solution for infrastructure and cloud environments. It offers discovery, relationship mapping, and integration with CMDB and ticketing systems. We use the product to integrate relationship mapping to CMDB in real-time and automate incidents. After monitoring the infrastructure and cloud, the product performs incident automation, including data center automation. We also use the product for remediation or diagnostic-level automation.
Assistant Management Specialist at a tech services company with 10,001+ employees
Real User
2022-07-06T14:16:00Z
Jul 6, 2022
I work for three companies where the usage is different. Earlier, the main usage is to monitor customer service. Later on, it was a tool used for a combination of both Splunk and ScienceLogic. Now it is different, and now we are using it to look for limited server monitoring. It's different in all the different ways I have been worked with the tool. However, basically, it's for monitoring for the most part.
ScienceLogic can be deployed on-premise and on the cloud. It is up to our clients what cloud provider they want to use. They can choose from many of the cloud vendors, such as Amazon AWS, Microsoft Azure, or Google Cloud. Most of our offerings are still using the IBM cloud. We are only using ScienceLogic for infrastructure. It can be for a small account, it could be a large account. Most of our large accounts are Fortune 500 companies. We have some of the large accounts around the globe, which are using ScienceLogic to manage their business.
Senior Consultant at a tech services company with 201-500 employees
Consultant
2020-10-04T06:40:14Z
Oct 4, 2020
We are using ScienceLogic primarily for monitoring our infrastructure, a few specific services like Citrix, and a few websites and their publication. We have private cloud deployments as well as on-premises deployments.
ScienceLogic is a comprehensive IT infrastructure monitoring solution that supports networks, servers, cloud environments, and applications, suitable for private cloud and on-premises deployments.
Organizations leverage ScienceLogic for its robust capabilities in monitoring IT infrastructures of all sizes. It offers granular discovery, integration with CMDB, and ticketing systems. Valued for its flexibility, incident automation, remediation, and real-time relationship mapping, it...
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 primary use case of ScienceLogic ( /products/sciencelogic-reviews ) for me is hybrid monitoring. This involves monitoring cloud infrastructure, data centers, or hyper-converged environments like Nutanix, as well as hardware monitors.
The primary use case is mostly centered around monitoring infrastructure and management.
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.
I use the solution in my company mainly for infrastructure monitoring.
We use the solution for monitoring networks, applications, and server environments.
We use the product to monitor our servers, network switches, and other devices. We can check if there are any issues with the patching.
The solution is a hybrid monitoring solution for infrastructure and cloud environments. It offers discovery, relationship mapping, and integration with CMDB and ticketing systems. We use the product to integrate relationship mapping to CMDB in real-time and automate incidents. After monitoring the infrastructure and cloud, the product performs incident automation, including data center automation. We also use the product for remediation or diagnostic-level automation.
We are using ScienceLogic for monitoring and orchestrating the remediation.
I work for three companies where the usage is different. Earlier, the main usage is to monitor customer service. Later on, it was a tool used for a combination of both Splunk and ScienceLogic. Now it is different, and now we are using it to look for limited server monitoring. It's different in all the different ways I have been worked with the tool. However, basically, it's for monitoring for the most part.
ScienceLogic can be deployed on-premise and on the cloud. It is up to our clients what cloud provider they want to use. They can choose from many of the cloud vendors, such as Amazon AWS, Microsoft Azure, or Google Cloud. Most of our offerings are still using the IBM cloud. We are only using ScienceLogic for infrastructure. It can be for a small account, it could be a large account. Most of our large accounts are Fortune 500 companies. We have some of the large accounts around the globe, which are using ScienceLogic to manage their business.
We are using ScienceLogic primarily for monitoring our infrastructure, a few specific services like Citrix, and a few websites and their publication. We have private cloud deployments as well as on-premises deployments.