We changed our name from IT Central Station: Here's why
Franco Fontana
Business Intelligence at UTE
Real User
Top 5Leaderboard
Supports different languages for querying the database and has a free version and community support
Pros and Cons
  • "The flexibility and the support for diverse languages that it provides for searching the database are most valuable. We can use different languages to query the database."
  • "It is hard to learn and understand because it is a very big platform. This is the main reason why we still have nothing in production. We have to learn some things before we get there."

What is our primary use case?

We are mainly using it for analytics reports for the data taken from our call center. We are using the entire stack. We are using Kibana and Elasticsearch. Kibana is the front end for dashboards, reports, etc.  

What is most valuable?

The flexibility and the support for diverse languages that it provides for searching the database are most valuable. We can use different languages to query the database. 

What needs improvement?

It is hard to learn and understand because it is a very big platform. This is the main reason why we still have nothing in production. We have to learn some things before we get there.

I have reported and had discussions about several bugs at discuss.elastic.co, but that happens with many products. It is not only with this product.

For how long have I used the solution?

We have been using it for about one year, but it is not yet in our production environment.

What do I think about the stability of the solution?

It is reliable.

What do I think about the scalability of the solution?

If you use a cloud platform or a cloud environment, it is easy to scale. 

For on-premises, we are using OpenShift. We are using a cluster on OpenShift, and we are facing some issues, but they are not related to Elastic. They are related to our infrastructure of OpenShift because OpenShift is deployed on VMware, and the storage of VMware doesn't allow us to take backup snapshots in a secure way. We are thinking of migrating this cluster of OpenShift to another platform.

Currently, we have a few users of this product because we have been using it only for one year, and we are the first ones in our company. In the future, we will have more people involved with the product.

How are customer service and support?

We have only used their community support from the discuss.elastic.co site.

What's my experience with pricing, setup cost, and licensing?

There is a free version, and there is also a hosted version for which you have to pay.

We're currently using the free version. If things go well, we might go for the paid version.

What other advice do I have?

It is a good choice, but you have to take your time to learn it. Its learning curve can be hard. 

I would rate it an eight out of 10.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Fares Zgheib
Lead Software Architect at a tech services company with 51-200 employees
Real User
Top 20
Easy to set up with good text indexing and logging features, but it needs to be more user-friendly
Pros and Cons
  • "The most valuable features are the ease and speed of the setup."
  • "Kibana should be more friendly, especially when building dashboards."

What is our primary use case?

The primary use case of this solution is for text indexing and aggregating logs from different microservices.

What is most valuable?

-Scalability and resiliency

-Clustering and high availability

-Automatic node recovery

What needs improvement?

Kibana should be more friendly, especially when building dashboards.

Stability needs improvement.

I would like to see the Kibana operating more smoothly, as Grafana does. Also, I would like to see some improvements with the machine learning capability, so that we can rely on it more. It's in the early phases but this would be a great way to start using it.

When it comes to aggregation and calculations, I would like to have to have advanced options in the dashboards to be used in a simplified way, such as building formulas and queries between different fields and indexes.

Alerting feature should be more flexible with advanced options.

For how long have I used the solution?

I have been using Elasticsearch for approximately five years.

What do I think about the stability of the solution?

This solution is stable, but at times the stack will freeze and you have to remove and recreate the cluster. It may be an issue related to AWS.

What do I think about the scalability of the solution?

We have not had any issues with the scalability.

How are customer service and technical support?

We have not had any issues with technical support.

Which solution did I use previously and why did I switch?

Datadog, it's expensive when it comes for a big infrastructure and cannot be self hosted when it comes to specific sensitive cases.

How was the initial setup?

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

What's my experience with pricing, setup cost, and licensing?

It can be expensive. When managed by AWS you have different options and features that are locked and not available to you on the Kibana and security levels.

You cannot use the full X-Pack feature set when you go through AWS.

What other advice do I have?

We have some devices that are managed by AWS and we have our own information with switches that are self-hosted.

ELK Elasticsearch is a product that I recommend.

I would rate this solution a seven out of ten.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Learn what your peers think about ELK Elasticsearch. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
564,997 professionals have used our research since 2012.
Ayesha Imtiaz
Senior Analyst at a tech services company with 10,001+ employees
Real User
Top 5Leaderboard
A very good product with good visualizations and stability
Pros and Cons
  • "I really like the visualization that you can do within it. That's really handy. Product-wise, it is a very good and stable product."
  • "They should improve its documentation. Their official documentation is not very informative. They can also improve their technical support. They don't help you much with the customized stuff. They also need to add more visuals. Currently, they have line charts, bar charts, and things like that, and they can add more types of visuals. They should also improve the alerts. They are not very simple to use and are a bit complex. They could add more options to the alerting system."

What is our primary use case?

We are primarily using it for monitoring. It is used for server monitoring.

What is most valuable?

I really like the visualization that you can do within it. That's really handy. Product-wise, it is a very good and stable product.

What needs improvement?

They should improve its documentation. Their official documentation is not very informative. They can also improve their technical support. They don't help you much with the customized stuff.

They also need to add more visuals. Currently, they have line charts, bar charts, and things like that, and they can add more types of visuals. 

They should also improve the alerts. They are not very simple to use and are a bit complex. They could add more options to the alerting system.

For how long have I used the solution?

I have been using this solution for one year.

What do I think about the stability of the solution?

Stability-wise, it is very good. Once the data starts coming in, it is very stable. I didn't find any big glitches in it.

How are customer service and technical support?

We contacted their technical support once. I didn't find them very good. They are there just to provide documentation and stuff. They don't help you much with the customized stuff. They could improve that. I would rate them a two out of five.

How was the initial setup?

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.

What was our ROI?

It seems good in terms of return on investment. It is a monitoring solution, and it triggers alerts before something happens. For example, it triggers an alert when the space in Windows reaches an 80% limit. I would say it is a good investment. We are able to fix things before they go wrong. If we didn't have Elasticsearch, things would go wrong, and we would be spending more time fixing them later on.

What other advice do I have?

I would advise others to first know Linux because it would most probably be on Linux. If you're good at Linux, you will be good at this as well.

I would rate ELK Elasticsearch an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
HimanshuTejwani
System Administrator and DevOps Engineer at a tech services company with 10,001+ employees
Real User
Top 5Leaderboard
Has a good UI with good performance although deployment requires multiple applications
Pros and Cons
  • "The UI is very nice, and performance wise it's quite good too."
  • "The different applications need to be individually deployed."

What is our primary use case?

Our primary use case of this solution is for monitoring our logs and infrastructure. We are customers of ELK and I'm a system administrator. 

What is most valuable?

A positive feature of ELK is that it directly interacts with Elasticsearch. The UI is very nice, and performance wise it's quite good too. A key feature is that this is a reasonably priced monitoring solution.

What needs improvement?

We run this solution on multiple servers. ELK has three lanes which comprise a single package made up of Elasticsearch, Logstash, and Kibana. To my mind, this is not efficient because we have to individually deploy the different applications. In contrast, we're able to deploy Splunk with a singe application. Implementing the dashboards is also quite difficult. With Splunk and Nagios it's much easier to directly interact with Elasticsearch. I'd like to see some additional features in the front end which currently make it a bit difficult to implement and it should be simplified.

For how long have I used the solution?

I've been using this solution for six months. 

What do I think about the stability of the solution?

This solution is stable. 

What do I think about the scalability of the solution?

This is a scalable solution, we have eight to 10 users. We had initially planned to expand use of ELK because of its cheap price and the services that are included, but given the difficulty with implementation we've decided to go with Nagios instead. 

How are customer service and technical support?

The technical support people are very knowledgeable but the response time is quite slow which is not very good. 

How was the initial setup?

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

What other advice do I have?

For anyone looking to implement a monitoring product with almost no cost or at a cheaper price, I would suggest the ELK stack. However, it does require a high skill set because of the difficulty with implementation. 

I would rate this solution a six out of 10. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Technical Manager at a computer software company with 51-200 employees
Real User
Top 5Leaderboard
A search and analytics engine that's very fast, but the price could be better
Pros and Cons
  • "I like how it allows us to connect to Kafka and get this data in a document format very easily. Elasticsearch is very fast when you do text-based searches of documents. That area is very good, and the search is very good."
  • "The price could be better. Kibana has some limitations in terms of the tablet to view event logs. I also have a high volume of data. On the initialization part, if you chose Kibana, you'll have some limitations. Kibana was primarily proposed as a log data reviewer to build applications to the viewer log data using Kibana. Then it became a virtualization tool, but it still has limitations from a developer's point of view."

What is our primary use case?

Elasticsearch is one of the NoSQL databases available. My application is a microservices application where the data gets published on a Kafka cube. It allows us to connect to Kafka and get this data in a document format very easily. I'm using Elasticsearch as my backend processing database, where I'm building and reporting using Kibana.

What is most valuable?

I like how it allows us to connect to Kafka and get this data in a document format very easily. Elasticsearch is very fast when you do text-based searches of documents. That area is very good, and the search is very good.

What needs improvement?

The price could be better. Kibana has some limitations in terms of the tablet to view event logs. I also have a high volume of data. On the initialization part, if you chose Kibana, you'll have some limitations. Kibana was primarily proposed as a log data reviewer to build applications to the viewer log data using Kibana. Then it became a virtualization tool, but it still has limitations from a developer's point of view.

For how long have I used the solution?

I have been using ELK Elasticsearch over the last two years.

What's my experience with pricing, setup cost, and licensing?

The price could be better.

What other advice do I have?

I would tell potential users that they have to locate the data source and understand the data. They will have to decide on whether they have to go for a NoSQL or a relational database. 

If it's NoSQL, then what kind of data are you seeing? If it's more textual data, then you're going to read more. So, I would recommend Elasticsearch. Otherwise, you have other databases like MongoDB and Cassandra.

On a scale from one to ten, I would give ELK Elasticsearch a seven.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Sudeera Mudugamuwa
Co-Founder at a tech services company with 1-10 employees
Real User
Top 20
Reliable, open-source, with good community support, and easy to install

What is our primary use case?

We use ELK Elasticsearch for storing application data logs.

What is most valuable?

Elasticsearch includes a graphical user interface (GUI) called Kibana. The GUI features are extremely beneficial to us.

What needs improvement?

Elasticsearch includes mechanisms for ingesting data into the cluster. So it would be great if those mechanisms could be simplified. Improving machine learning capabilities would be beneficial.

For how long have I used the solution?

I have been working with ELK Elasticsearch for four years. We are using the latest version.

What do I think about the stability of the solution?

We have no issues with the stability of ELK Elasticsearch, it's quite reliable.

What do I think about the scalability of the solution?

What is our primary use case?

We use ELK Elasticsearch for storing application data logs.

What is most valuable?

Elasticsearch includes a graphical user interface (GUI) called Kibana. The GUI features are extremely beneficial to us.

What needs improvement?

Elasticsearch includes mechanisms for ingesting data into the cluster. So it would be great if those mechanisms could be simplified.

Improving machine learning capabilities would be beneficial.

For how long have I used the solution?

I have been working with ELK Elasticsearch for four years.

We are using the latest version.

What do I think about the stability of the solution?

We have no issues with the stability of ELK Elasticsearch, it's quite reliable.

What do I think about the scalability of the solution?

ELK Elasticsearch is a scalable product

This solution is used by five to ten people in our organization.

ELK Elasticsearch is used on a daily basis.

How are customer service and support?

We have not contacted technical support.

We had a couple of issues that we were able to resolve by looking up the public information that is available on the internet.

There is a lot of community support for this solution.

How was the initial setup?

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.

What about the implementation team?

We completed the implementation internally.

What's my experience with pricing, setup cost, and licensing?

Although the ELK Elasticsearch software is open-source, we buy the hardware.

What other advice do I have?

The distributed installation is the way to go.

I would rate ELK Elasticsearch a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
Kumar Mahadevan
IT Infrastructure Analyst at AG Group
Real User
Top 5Leaderboard
Powerful, graphical, good customer support and full featured
Pros and Cons
  • "You have dashboards, it is visual, there are maps, you can create canvases. It's more visual than anything that I've ever used."
  • "I have not been using the solution for many years to know exactly the improvements needed. However, they could simplify how the YML files have to be structured properly."

What is our primary use case?

I am using this product for a SIM solution.

What is most valuable?

Their anomaly detection engine is really good for example, compared to SolarWinds. You can ingest different pipelines. You have dashboards, it is visual, there are maps, you can create canvases. It's more visual than anything that I've ever used.

What needs improvement?

I have not been using the solution for many years to know exactly the improvements needed. However, they could simplify how the YML files have to be structured properly. If you want to ingest certain logs, you need to edit the YML file and connect it to your modules to start ingesting and parsing the end-user logs. Doing this is sometimes difficult and could be streamlined.

For how long have I used the solution?

I have been using the product for approximately three months.

How are customer service and technical support?

The customer service is very good.

Which solution did I use previously and why did I switch?

I have used SolarWinds in the past.

What other advice do I have?

The solution has a lot of features. They have machine learning jobs they can implement, I'm not there yet, but I can use anomaly detection to see there are various processes that can find users that aren't supposed to log onto certain machines. All of these features are visual and graphical. I can show it as a bar chart, a pie chart, I can Instagram, or I can split chart. The power to see everything on the front end is so much more powerful.

I rate ELK Elasticsearch a ten out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
IT Secuirty Architect at a insurance company with 10,001+ employees
Real User
Top 20
Valuable detection and correlation features
Pros and Cons
  • "The most valuable features are the detection and correlation features."
  • "Something that could be improved is better integrations with Cortex and QRadar, for example."

What is our primary use case?

We are internal integrators. We are in the bigger group as of now, but other groups, our clients, are affiliates from our group. They are our internal clients. 

The solution is currently on-premises.

I was mostly responsible for the SOC team, and I helped them create the detection rules for the production. I wanted to know how it could be implemented in different kinds of products, like Sentinel.

What is most valuable?

The most valuable features are the detection and correlation features.

What needs improvement?

Something that could be improved is better integrations with Cortex and QRadar, for example. 

For how long have I used the solution?

I have been using this solution for no more than one year. 

How are customer service and support?

Not really, because I'm not the engineer and so most problems appear during the installations or maintenance and I'm not in developing infrastructure operations.

What's my experience with pricing, setup cost, and licensing?

The price of Elasticsearch is fair. It is a more expensive solution, like QRadar. The price for Elasticsearch is not much more than other solutions we have.

Which other solutions did I evaluate?

I would say that Elasticsearch is better than all the other solutions. QRadar is getting better, but it is still behind Elasticsearch in my opinion.

What other advice do I have?

I would rate this solution 8 out of 10.

I would recommend Elasticsearch if you don't have bigger budget limitations to use other enterprise solutions or if you want to avoid the vendor lock-in.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate