View full review »

Initially, deploying Elastic Search was a bit challenging for me as it was my first time using the Elastic Stack. Setting it up to monitor traffic on multiple VMs, including an enterprise-level VM, posed some configuration hiccups, especially when connecting to the cloud. I had to rely on online resources and Google searches to troubleshoot and figure things out. While I eventually got through it, the process felt overwhelming with lots of information to digest at once. As for maintenance, during the short period I used it for a lab, there wasn't much to handle beyond shutting it down and reinstalling it at the end. I can't speak to long-term maintenance since my usage was relatively brief.

View full review »

The initial setup was straightforward.

View full review »

Deploying in Kubernetes is not complex. There are many resources in the market, like DevOps guys and guides, which make the process straightforward. The deployment can be done in a matter of minutes. You basically run a configuration file to set up your application, define replicas, and so on. It shouldn't take much time; even with an expert, it's a matter of a few hours. 

However, the key lies in following best practices and configuring your files properly. If you follow the best practices, you'll likely face fewer issues. But if not, problems are inevitable. 

It’s crucial to analyze these practices, considering factors like bandwidth, data volume, user interaction, and how it's read by different applications. These considerations help in managing resources and scalability, including scaling up and down your Elasticsearch container. These points are vital for running Elasticsearch efficiently, especially for text-based search applications.

You can deploy it as required. Elasticsearch is versatile; you can run it on Kubernetes, in the cloud, or on-premises. There is no limitation in terms of deployment options.

View full review »

I can't speak to the initial setup. The infrastructure team handled the setup. I did not implement it directly.

It is my understanding we needed three or four engineers to handle the deployment and maintenance process. 

View full review »

The initial setup is very easy.

We took about a month to deploy the solution. 

We might need about ten people to handle the deployment and maintenance. We're still in the test environment right now. 

View full review »

The initial setup is not complex to me. I've seen it displayed before in a demo presentation with Jakadaz. The solution is not difficult to use. It's very easy. Even as a non-technical person, I could interact with the application. View full review »

The initial setup is difficult. On a scale of one to 10, with one being very difficult and 10 being very easy, I would rate Elastic Enterprise Search a two. 

We are continuously integrating new features. Everything we added this month took about a day each to deploy. We have 22 software engineers on the project, along with two tech leads and one solution architect.

View full review »

The initial setup is difficult because the solution is an independent product that requires integration with the running system. A one-time configuration is needed for both cloud and on-premises systems. This is common for independent products so is not a big deal for our company. 

For comparison, Stackdriver is already built in the GCP so there is minimal configuration when deploying services in the GCP environment. 

View full review »

The initial setup of Elastic Enterprise Search was straightforward.

View full review »

The initial setup has a moderate amount of difficulty. It's not simple and not overly complex. 

View full review »

Elastic Enterprise Search is of a moderate range of difficulty, it is not difficult and not easy.

View full review »

The setup of Elastic Enterprise Search is not normally easy but I was running it on top of Docker which made it easy.

I rate the initial setup of Elastic Enterprise Search a three out of five.

View full review »

The initial setup is very straightforward. It's not difficult as well. 

View full review »

The product's setup is difficult. 

View full review »

The setup is straightforward - although Logstash needed extra care in Windows VM installations.

View full review »

Initial setups were complex years ago, but they are more straightforward in the current offering. ELK is essentially a collection of products that each requires infrastructure and expertise to set up independently, and connecting them to gain a functional tool requires still more expertise.

View full review »

The initial setup was very easy. I rate the ease of setup an eight out of ten. The setup can be done within minutes.

View full review »

In our case, it was a simple installation process. It was just set up in small environments, however, if it's getting larger, it will be more complex as then you have to split all the different roles onto different machines, to get the performance you need.

Therefore, for small environments, it's very easy. If you're doing a big environment, then it's much more complex.

The only maintenance needed is for updating the systems. We're working on it to make it all more or less automatic. All we need to do is to implement the updates when they arrive.

View full review »

Initial setup is indeed straightforward and fast because it will mostly be a single-node cluster. But as the data volume grows and we start seeing a performance lag, the stack requires scaling (by adding more nodes) and a professional intervention for doing the right capacity design and configuration fine tuning.

View full review »

The product's deployment took a couple of days to complete. 

View full review »

I would rate the initial setup process as a five out of five because it's the easiest product I've ever dealt with. When it needs to be upgraded, you just tell it to upgrade and the solution does it for you. 

View full review »

We had issues when we first did the initial setup, because our resources were limited because it was a test that it was a proof of concept. It meant the initial setup was somewhat resource intensive. The data NGS itself was an issue when we were trying to filter and pull that information. Again, a signature analysis would have been helpful here.

View full review »

It is complex because it is not Windows-based. It is Linux-based, so one must know Linux to deploy it properly. It is not a product that you can install with just multiple clicks. You need to understand it.

View full review »

The initial setup for the SaaS platform is quite easy. We took assistance from an engineer for the onboarding. Thus, it was straightforward for us. However, there could be a better integration with AWS.

I rate the process a seven out of ten.

View full review »

Setup was a little complex, but we had in-house expertise.

The solution needs regular fine-tuning in terms of the data model. As we get more and more data into the system, the predictability and accuracy of the output keeps changing. On the application and DB side, it was fine. Not a lot of maintenance was required.

View full review »

The initial setup is straightforward. If you understand Linux you can deploy in a couple of days.

View full review »

Its initial setup is straightforward. There were no problems.

View full review »

You need three resources to handle the deployment. 

View full review »

It's easy to install the servers, that's not really the problem. The difficulty is afterward. Users need to understand how to explore the data.

The server setup is the easy part. Even, let's say, moving the log into the machine or into the database is no problem. However, then you have all this data and you will really struggle to understand the information. That is sometimes not always obvious at the outset. In order to do that in an effective way, it requires a little bit of manipulating.

To install the servers, a minimum installation takes me a day or more. It's for the most part usually pretty fast.

View full review »

The tool's deployment is easy. It took us one day to deploy a seven-node Elastic Search cluster. 

View full review »

The setup is straightforward for PoC, but becomes complex while scaling it or deploying it for production.

View full review »

The initial setup had a bit of a learning curve for us while we acclimated ourselves to the use of the solution. However, after a while, it became quite easy. 

I would not say there was much complexity even at the outset, as we have an understanding of how to troubleshoot and do the installation.

There is more than enough documentation of the solution online. It is useful and you can find what you're looking for. There are also forums that can be of assistance. 

View full review »

The initial setup is simple, not too difficult. 

Getting the index, doing your models, and putting the data in, correctly, is done more on a trial and error basis. You have to start early and plan it well to get it right.

View full review »

The initial setup was okay, not as easy as Splunk but it was manageable.

View full review »

The initial setup of ELK is more difficult than the setup of other monitoring applications. I was able to carry out the deployment alone. 

View full review »

The initial setup was straightforward and quite simple.

The installation took between six and eight hours to complete.

There is no maintenance required other than regular updates.

View full review »

We did not have difficult trouble installing and configuring Elasticsearch. The setup is straightforward.

View full review »

Slightly complex, especially when you are configuring a machine which is on a separate IP, rather than on a single machine. In my case, Elasticsearch, Kibana and Logstash were on different machines. Along with that, we added a proxy server (nginx) ahead of the Kibana server. We used the proxy server for user authentication so that only known users would be able to access the Kibana dashboard. ELK's free version doesn't have user authentication, and this forced us to go with this alternative. We have four machines in total.

When we were using the Amazon Elasticsearch Service we had one cluster of Elasticsearch which, by default, gave us the Kibana dashboard. We just added a proxy server for user authentication.

View full review »

All the installations were directly set up on the local servers.

View full review »

Our initial setup was very easy to do.

View full review »

The initial setup is straightforward, it took about an hour. I did the setup myself. Some others also did it themselves and we had developers who put it up in the cloud for the others. 

View full review »

The initial setup of this solution is easy and straightforward.

The deployment is both easy and quick.

View full review »

The initial setup was easy because we used containers. It can be challenging to implement.

View full review »

The initial setup was fast. We have the provisioning, which made it fast and easy.

View full review »

The initial setup is not that problematic. It is obviously manageable as we are doing it by ourselves, so it is okay and fairly straightforward. We didn't need any assistance from integrators or consultants for the deployment.

View full review »

The initial setup of this solution is a little bit hard. I did not find it hard, myself, but it was difficult for my colleague who had less experience.

The deployment takes between one and two hours.

View full review »

The initial setup was straightforward.

View full review »

The initial installation and setup were straightforward. It will take a few minutes to deploy.

View full review »