Elastic Observability Reviews

Our clients use the product for monitoring and alerting.

What I like the most about the tool is that we have access to all solutions through it. The product has connectors to many services. It is very open.

The cost must be made more transparent. Sometimes, we create a cost plan, but it doesn’t match.

I have been working with the product for the last three years. I am working with the latest version.

The tool is stable. We have no problems. I rate the stability a ten out of ten.

I rate the tool’s scalability a ten out of ten.

The technical support is good.

Positive

I rate the ease of setup a ten out of ten.

I rate the pricing a five out of ten. The product is not that cheap.

We resell the solution to our customers. It is a good solution. I like it. Overall, I rate the product a ten out of ten.

Elastic Observability significantly improves incident response time by providing quick access to logs and data across various sources. For instance, searching for specific keywords in logs spanning over a month from multiple data sources can be completed within seconds.

I can quickly check connectivity for endpoints to identify whether network or endpoint issues are causing problems. Access to logs also allows me to monitor hardware status and identify any anomalies affecting performance.

The benefits of using the product are numerous. You can effectively monitor your environment and applications. You can track response times and network performance. It enables you to manage alerts and security rules, enhancing overall system security.

The tool's scalability involves a more complex implementation process. It requires careful calculations to determine the number of nodes needed, the specifications of each node, and the configuration of hot, warm, and cold zones for data storage. Additionally, managing log retention policies adds further complexity. The solution's pricing also needs to be cheaper. 

I have been using the product for six months. 

The product is indeed stable, but monitoring storage regularly is essential. Monitoring storage usage lets you track how many logs are collected daily. 

The product's technical support is great. Even the community forums are helpful, where users can post their questions or issues and receive responses

The tool's implementation is straightforward. 

I rate the overall product an eight out of ten.

We use Elastic Observability for system monitoring, server monitoring, and application monitoring. I'm working on a project wherein I use the solution for capacity planning.

I have built a mini business intelligence system based on Elastic Observability. We show all the real-time transactions, the transaction type, the transaction amount, and different kinds of metrics based on different transactions. We've built something that helps our different teams working with the same stack make everything visible using Kibana. This helps the compliance team to track some Visa card transactions, etc.

Elastic Observability’s price could be improved.

I have been using Elastic Observability since 2015.

Elastic Observability is a stable solution.

Currently, Elastic Observability is scalable because the client needs to see things working before agreeing to scale the solution.

I am the only guy involved with the solution's deployment.

Users have to pay for some features, like the alerts on different channels, because they are unavailable in different source versions.

The project requires monitoring and tracking everything, including some internal services with the SAP application. The project manager needs the capacity planning dashboard to help him reduce the cost on the cloud.

Overall, I rate Elastic Observability a nine out of ten.

The primary use case for our organization is handling login events. We also utilize it for some big data use cases.

Elastic APM help us anticipate and have a more accurate view in our IT exosystem. We deploy it specially for two mobile applications at the beginning. 

In addition to the fact that we are more proactive in the detection of incident before they occur, we can on one click see the request path from the customer to the backend. It is very useful and permits us to gain time. 

Before Elastic APM, we had to connect to different servers to check where is the issue. Now, we gain about 2h.

The solution is more of an optional variety platform. It's more than an APM platform. It goes further than that. I'd describe it as a more complete tool. 

The licenses are unlimited and based on the number of elastic search hosts contrary to the other solutions that are working in a model for a license for each instance monitored, for example, which is actually a very good thing. 

The price is very less expensive compared to the other solutions.

Our licensing model isn't a full one. We are in a less interesting model, so we do not have intelligence on it. We don't get system intelligence and machine learning models, however, I don't know if it is relevant to what we use the solution for. 

We don't have the platinum version. We are on the gold version. Our system intelligence and machine learning, and the other things regarding the competencies of everything, we have to build ourselves. It's not easy, as we are in West Africa and sometimes we do not have the relevant competencies. It takes time to get the skills we need to use the solution effectively.

The solution would be better if it was capable of more automation, especially in a monitoring capacity or for the response to abnormalities.

I've been using the solution for about one year now. It hasn't been too long.

The stability of the solution is decent. There aren't crashes. I don't recall experiencing bugs or glitches.

We currently have a gold subscription. In the platinum subscription, normally we have a Kubernetes version, so the scalability is built into it. With gold, we do not have the scalability capability. We do not have the top subscription license.

That's not to say the solution can't scale. You just need to have the proper subscription if that is your organization's goal.

We've had issues in the past and have had to reach out to technical support. They were helpful. We've been satisfied with the level of support we've been getting. It's been great.

The initial setup is simple, however, you need to have the resources necessary to set it up. We are working in an open source environment. It's simple, but it's a long process. You have to build the core competencies to be able to build the solution. This part is difficult, or, at least, can be difficult for some organizations.

We took approximately three months to run a POC (Proof Of Concept). Then, we started to work with it by covering one application stack. We have covered approximately three applications. This was done over the course of six months. 

However, how long it will take depends on the core competencies that you have and that you are working with. If you have the core competencies necessary, it would go pretty fast.

We are using the open source version, so there's been no need to build anything ourselves. We do not have a lot of casual issues, and, compared to other solutions like AppDynamics, Dynatrace, and New Relic, it's much cheaper. The costs are very, very affordable.

Before choosing, we compare the solution to Dynatrace, New Relic and App Dynamics. We had a demo for each solution and compared the prices. We notice that these solutions had almost the same functionnalities. The difference was probably in the effort cost to deploy and implement the different use cases. We choose Elastic for the pricing and the fact that it's include the stack for log and event management.

We're a customer. We don't have a professional relationship with Elastic Path.

The solution is fantastic. I would rate it nine out of ten. It's practically perfect for our purposes and meets our needs. We still have to build it out. We're relatively new to using it.

To make it a perfect ten, for me, the ideal solution would be one that could automate a bit more for monitoring of our whole information system. If we could deploy something, and then discover automatically all our stacks or all of our infrastructure (like the one agent for Dynatrace), it would be perfect. 

Overall, I would recommend it. It's the most cost-effective. However, If you do not have an on-premise infrastructure, and you want to work on the cloud, or maybe you don't want to be involved in the management of the software as a service solution, you can look for software solutions like Dynatrace, AppDynamics, or New Relic.

New users will need to ask: do I have the core team with the core competencies? It may be the most cost-effective solution, however, it's really important to have the core competencies required, or you may run into issues.

We basically use Elastic APM for our metrics to look at our performance. Whenever people say that there's a latency of more than a certain amount, then we just open this APM and see why exactly the latency is high. We can choose that data set, and then we can go deeper. 

The solution allows us to track performance via metrics.

We're able to see where latency is happening. 

The solution allows us to dig deep into data.

There needs to be less boiler code. That's where I see a solution such as Dynatrace as being very good. We need to just deploy the Dynatrace and then it just uses all the TCP packages et cetera, to figure out what the endpoint to endpoint mapping is. It can give more insight into performance.

I can see mistakes in annotations. If a developer uses a different annotation, these performance metrics are not in the portal. When I go to the portal, I do not see many insights on the endpoints or where there could be latencies. I'd like overall fewer mistakes.

The solution needs to use more AI. Once the product onboards AI, users would more effectively be able to track endpoints for specific messages.

I do not have more than six months' experience with this solution. I'm a senior engineer here and I just was looking at a few issues in our system, and then I could see that how we are doing this APM integration.

I may not be able to comment on the stability as that is something DevOps should know. My understanding is that it is stable. That said, in use cases, it lacks insights features. 

I came to this organization from a financial background. In all the major banks, capital markets, they use this ITRS Geneos. I have experience in that tool.

I don't have any details in terms of pricing. It's not an aspect of the solution I am familiar with. 

I see that there are a few features that are not there in that Elastic APM. I have been looking at another APM that we can use in our C systems.

I am looking into Dynatrace and Azure Monitor.

We are just a customer and an end-user.

With so little experience with the solution so far, I do not have any specific advice to share with others. 

I'd rate the solution at a six out of ten.

We are using Elastic APM primarily for central logging.

Elastic APM has plenty of features, such as the Elastic server for Kibana and many additional plugins. It's a comprehensive tool when used as a logging platform.

In the future, Elastic APM needs a portfolio iTool. They can provide an easy way to develop the custom UI for Kibana.

Elastic APM needs to focus on improving infrastructure, monitoring, and enriching Kibana features.

I have been using Elastic APM for approximately one year.

Elastic APM is a stable solution if it is configured properly.

The scalability of Elastic APM is good.

The solution is good for small businesses but not good for enterprises or corporations. There are other tools that would be better suited.

The is a comprehensive online community that I have used for support.

The implementation of Elastic APM is highly complex. However, the setup is straightforward for Docker installation or containers. The multiple cluster configuration with the distributed nature of the solution is difficult.

I have evaluated Dynatrace and it's an amazing solution compared to Elastic.

I would advise others to use a different solution than Elastic APM. 

I rate Elastic APM a six out of ten.