On a scale of one to ten, I’d give it six in terms of ease of setup. We don't need to have some level of engineering expertise. It's not as straightforward as rolling out a Power BI or a Tableau, for example. Also, the infrastructure is multilayered, and it is complex. The rollout should have some level of engineers involved.

For us, the deployment took about two weeks.

It is easy to set up the solution.

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.

Implementing ScienceLogic as a monitoring tool was quick. It took us approximately six to nine months, plus another 20 months to link it to our automation framework.

There are two types of architecture. One is an all-in-one, and the other one is like a distributor. We went for the all-in-one option. It's very easy to set up. The distributor is a bit more complex. However, items like message collected, data collected and admin portal and database are like deploying one component at a time. Once we deployed them, we needed to connect to them. We needed support during that period. We needed a team. 

The deployment is quick. We could do it over a few hours on a Sunday.

We were working on the cloud; our entire infrastructure was set up on the cloud, and we were using the Azure cloud. Our overall architecture was built on the Azure cloud. We also had specific collectors. ScienceLogic has three layers.

The collection layer, the main servers, the user interface or administration portal, and the database layer were all always based on Azure, but the collection layer was deferred. We also deployed the collection layer and message collection at the Azure, GCP, and AWS levels. Our infrastructure was mostly cloud-based. This was a private cloud environment for the company I worked for, as we never used a public or shared cloud environment.

The initial setup is not complex at all; in fact, it's quite simple. It's fairly straightforward because we already have the binary and images. There is nothing complicated about enabling the ScienceLogic environment.

When I deployed it for the previous company, there were only three of us. We also never worked together because we had shifts and a ScienceLogic support team that was initially assisting us on a few buildings. Because the support team is spread across the globe, two people had to work on the US shift, a few on the EMEA shift, and a few on the India shift. We had to report to management during the EMEA shift because the company is based in Switzerland, and we had someone to report all the issues and handle all the requests from the customer and other stakeholders. But, to be honest, you don't need much; it all depends on the environment, and how big your environment is. As the previous company is a large environment, we only had three resources working around the clock.

Initially, prerequisites must be met, we worked with the Azure team to open up all Firewall requests and such. The length of the process varies from company to company. After all of the prerequisites were met, it didn't take us a long time. Because we only needed three layers, the entire environment was built in about two weeks. The administration portal, the database layer, and the collection list are all available. There were two collection layers. The first was a message collector, and the second was a data collector.

Message gatherer, It's similar to an SNMP-based collector. It gathers information. It does not send any data. The data collector will collect data from other servers. When I mention servers such as AIX or Windows, or servers that send you data, I mean that all data is accumulated in this data collector. However, there are some devices, such as network devices, that continue to send without being asked. A message collector is required for these data.

Initially, when you try to implement an environment, not everything happens at once. You must take it one step at a time. The customer will initially advise if they want to go ahead with AIX or go ahead with Linux or go ahead with what is the easiest. An environment contains numerous elements, such as storage, network, Windows, AIX, Linux, hubs, switches, and a variety of other components.

We first decide which ones will be the first to be discovered. As a result, we develop data collectors. We continue to add data collectors as the load increases. You cannot decide that we need this many data collectors all at once. However, you should have the inventory ready when planning the implementation. In terms of the initial inventory, you will know how many data collectors to install. You begin with those items and gradually expand your data collector. However, as I previously stated, I believe that two to three weeks is sufficient for the initial setup.

When we talk about maintenance, we have to keep checking because the IT environment changes so quickly. We have a lot of switches, and a lot of child components coming or attaching to the appliances, and in those cases, we must constantly monitor the RAM, how it is being used, how loaded it is becoming, and how many child devices are being added, and so on. 

When it comes to maintenance, we don't have to think about it because ScienceLogic has its own dashboard. You can add widgets to the dashboard, as well as all of your components, such as collectors, data collectors, message collectors, portals, and database layers. You can create a check in your dashboard.

On a daily basis, you can simply go to the dashboard and see how your environment is performing. It keeps alerting you that the file system is now full, or that we are using too much RAM, or that the processor is being overworked, and so on. It alerts you. We can create a dashboard like that. 

There are some things that we need to check on a daily basis such as the collector because collectors are responsible for collecting data. Occasionally, too much data is loaded during data collection. That is when we must investigate. 

We have this dashboard, and you can create your own. You continue to check your health on a daily basis. Whenever you decide to start working on any product, not just ScienceLogic. There are always these health check scripts, health checks, or dashboards. You can create that and have something ready or, actively look into it on a daily basis, and avoid unwanted situations.

The solution is deployed on the cloud.

The initial setup is pretty straightforward. Deployment time depends on the infrastructure. If you have less than 1000 servers, then the setup doesn't take long and can be completed within a few weeks. A larger deployment will take longer. 

The initial setup is very complex.

The setup is straightforward. It is easy to manage and check for alerts. The classification of alerts is specific. It makes it easier for admins to manage alerts. We can quickly identify what is critical and a warning-level alert. We move the managed servers across the network while migrating the clients' data from other products to ScienceLogic.

The initial setup is straight forward from a high-level. We received assistance from ScienceLogic on the initial installation / configuration. I was not involved in the actual deployment but it sounded like it went well.

The initial implementation of ScienceLogic is straightforward because often we use our cloud services and the only thing we need to do is add collectors on the client's environment and then connect into the cloud offering. The installation of the collectors and making them connected to the network into the servers that we have on top of the cloud is not complex.

It is easy to set up. It is a SaaS product and has agentless monitoring. From a setup perspective, it is easy.

The deployment depends. It can be set up in two weeks or six weeks. However, normally, we're seeing the deployment done in two to three weeks. It's a quick deployment that is happening. It all depends upon the environment and the requirements that need to be there. Generally, it's a quick deployment.

Straightforward, but once you get past discovery you have to learn how to setup monitoring and event messages. There is a lot of automation as discovered, but you have to understand what is automatically setup and why. Then you can look at customizing things for your environment.

It was basically straight forward to get up and running. Assuming networking and firewalls are open appropriately it can be setup and providing value within hours.

The overall setup was straightforward and designed with ease in mind.

The initial setup was rather simple. We used Professional Services as well as Technical training resources from ScienceLogic.

Our deployment was straightforward, however we had gone through ScienceLogic’s professional training prior to deployment allowing my team to understand the product prior to deployment. I believe it would have seemed much more complex without the training that we had been given.

The initial setup was straightforward.

The HA or DR deployments introduce some minor complexities, however the deployment team stands ready to assist with any issues that are encountered, or can deploy with you onsite.

The initial setup was very straightforward. When we purchased the product they deployed a knowledgeable architect to assist with standing up our environment. He worked with us to customize to meet the needs of our company. After the initial standup, I was able to stand up a lab environment without any assistance from ScienceLogic support. That's how easy it was!

Very simple to roll out. Have not had any issues with initial installs or any updates. The hardest part for us was configuring SNMP across hundreds of Unix servers which took some scripting.

Nothing we do is straightforward. That's just the nature of operating at the scale that we do. I can tell you that over the course of nine months with a tremendous amount of input from their and support from their team in terms of design and implementation and architecture, we were able to migrate, I want to say, around fifteen thousand devices from a legacy monitoring platform into EM7 without missing a beat. You think about a nine-month project, you consider the amount of time that went into that. Nine months sounds long, but I don't think it is. I thinks that's probably less than it should have taken, and certainly less than it would have taken with other platforms.

The initial setup is straightforward and very easy. Just mount its media and follow all the steps.

 It is straightforward.

Very easy and straightforward.

Initial setup is very straightforward. Appliances with prebuild system are being shipped to you (either All in one for smaller customers or collector, database and API for anyone with few thousand devices.) System is pretty much plug and play and required only few hours of setup.

Very simple. With the auto-discovery capability, I didn't have to created complicated configuration files like with Nagios.

The initial setup was straightforward with the assistance of deployment support. It was a very educational setup.

Again, I was not part of the initial setup I joined my company after things were originally launched.

Easy to follow plus they allow for a rep to assist with the install.

It was complex - it required their technicians to assist on setting up the system initially.

Simple.