What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
I've used SolarWinds, Datadog and Grafana, but ScienceLogic has a particular architecture that is difficult to understand. There may have been some improvements, but the fundamental architecture around the design is different from other tools. All the other solutions have similar architecture like S&P and OIDs and play with the same four underlying technologies. ScienceLogic, however, is not very user-friendly. It has very interesting design paradigms but is not the easiest to use until you understand it.
Regarding additional features, it would be great if ScienceLogic could improve its notification feature. The company had a good-sized network team of about 30 people. However, only about two or three people did most of the work in ScienceLogic. For example, somebody would re-patch cables or turn up a new switch, and they wouldn't change the things in the monitoring tools. Instead, they would physically change the equipment or the configs. Also, if we didn't have proactive communication, dashboards would break, graphs would stop working, and alerts wouldn't fire because no one was aware. Therefore, some notification would have been helpful. For example, some tools send notifications saying, "Hey, this isn't working anymore. Do you want to do something about it?". ScienceLogic has a tiny little icon that looks like a bomb. If you go into a dashboard panel, it will say, "Hey, missing data." But aside from that, it is just a blank dashboard panel. It doesn't notify us to say, "Hey, I'm no longer receiving data," So I would recommend a proactive notification feature.
In addition, we lobbied for a Runbook automation feature for a long time and were told it may be included in a future release. I am unsure if they have included it now. We wanted it completed overnight when we had offshore people working and during the day when the actual engineers were on the phone or in the office. But they couldn't complete time-based, contextual Runbook automation. We argued with them for about a year and a half, so I hope it has been included.
For how long have I used the solution?
We used this solution for about seven years at my previous company. I moved to a new company two months ago. The solution was deployed on-premises.
Buyer's Guide
ScienceLogic
March 2026
Learn what your peers think about ScienceLogic. Get advice and tips from experienced pros sharing their opinions. Updated: March 2026.
885,264 professionals have used our research since 2012.
What do I think about the stability of the solution?
The stability was very good, and we only experienced one isolated issue. The stability was good because we were versions behind with ScienceLogic for about a year and a half, rebooted it every other week, and it still ran fine for years. So realistically, all things considered, I would say it's more resilient than average for the products in that market.
What do I think about the scalability of the solution?
The solution is scalable, but it was challenging onboarding users to ScienceLogic even if we gave them an AD and put them in an AD group. The user would log in, fail, and their profile would lock. It would then create a nonfunctional profile, and we would have to go to that profile and assign them a read-only, administrator, or power user level. Then, we would have to give them access after they logged in or tried to log in and failed. It was an issue for several years and made it difficult to onboard new users. ScienceLogic should have a good access control model that does not rely on just locking the user out. We had about 30 users that actively used the solution, but about five to eight were administrative users.
How are customer service and support?
I rate the technical support a six out of ten for break-fix issues. However, their installation assistance was better when we upgraded, and I rate that an eight out of ten.
How was the initial setup?
The initial setup was average. It was not difficult to turn on. We had a dedicated appliance that was very easy to use. You plug it, turn it on and give an IP address.
The second time we set up Science Logic, we put it on a VM. Turning it on was pretty straightforward but getting it configured was a Herculean task and a lot of work. It was a very manual process apart from the power packs, which give you specific settings that make some of it easier.
So, if you want to use ScienceLogic, you need to include the costs of a minimum of two consultants for six months, depending on the size of your network or hire one person full-time to take care of it. It is a lot of work. For example, people re-patch a cable, and you have to change labels, or weddings show up on your graphs, which requires upkeep.
What was our ROI?
I am unsure of the exact ROI. Other solutions are cheaper, but for a national enterprise, it may be worth it to pay. When a branch network was down, it became costly to manage. ScienceLogic was good at proactively identifying problems. When a branch was down, ScienceLogic will act and turn a 45-minute outage into a 20-minute outage, or they would see the early warning signs and solve it in advance. We had about eight occurrences where our branch network was down, and ScienceLogic reduced the outage length for about three of them.
What other advice do I have?
I rate this solution a seven out of ten. It is as good as any tool on the market for true network monitoring and robust features. It is flexible and relatively extensible, but it is not easy to use.
ScienceLogic is slow to adjust to a rapidly changing market as everything is moving towards a holistic SRE approach. ScienceLogic is moving in that direction with the change ticket system, change tracking system pipes into a Datadog or a BigPanda and AI ops tools, but they are not keeping pace with the market.
We chose this solution because we knew how it worked, and the core competency of ScienceLogic is its core network monitoring functionality. It provided the needed features and bridged the gap between our distributed branch network and quarter enterprise network, which was sufficient.
If someone were using this solution for the first time, I would recommend getting a consultant and understanding what matters to the business. The business needs should dictate the monitoring. You need to ask questions like, How long does it take to load? When does the network circuit blip? Are the servers overloaded? It would help if you also had an expert who could understand the tool and have answers to these questions. If you already have a knock engineer or an SRE, ScienceLogic, it would be difficult for them to understand the tool. You may have to pair somebody who knows the business, needs and environment with somebody who has all the ScienceLogic expertise.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.