Elastic Observability Reviews

We use the solution to collect logs. It also helps us with application performance monitoring. We use it for centralized logs and visualizing them with Grafana.

The tool's most valuable feature is centralized logging. Elastic Common Search helps us to search for the logs across the organization. 

Elastic Observability needs to have better standardization, logging, and schema. 

I have been using the product for three to four years. 

I rate the tool's stability a seven out of ten. 

I rate Elastic Observability's scalability a six out of ten. 

We chose Elastic Observability since it was the industry standard. 

The tool's deployment was complex. 

Elastic Observability has helped us improve time and efficiency. We have seen ROI with its use.

I rate the overall product an eight out of ten. 

Machine learning is the most valuable feature of this solution.

Because it is an open, enhanced APR, no custom integrations are required. They're open, so it's an open-wear product that's simple to use and evaluate.

They need more skills in the market. There are not enough skills in the market.

It is not pervasive enough on the market, in my opinion. In other words, there isn't a big enough user base. 

The development of new features, functions, and releases, is not necessarily based on market demand. Which is why I can't rate it a 10 because of that. 

In my opinion, because there are not enough skills, the skills are still expensive. The software and the platform may be affordable, but the skills to deploy and manage it are expensive.

I have been managing teams that use Elastic Observability for 36 months.

It's an AWS platform as a service, so it's obviously as stable as AWS.

Elastic Observability is a scalable solution.

We have approximately 500 users in our organization.

I have contacted technical support and I would rate them a five out of five.

It is a Platform As A Service (PaaS). It's challenging because, in a platform world, you have to have your own abilities. You don't rely on the vendor for help unless something goes wrong.

I have not personally used but I have led teams that used App Dynamics, Dynatrace, Elastic, Splunk, ServiceNow, DXAPM, and Tivoli.

We implemented it in a complex environment, so whether the tool was simple or complicated was irrelevant. Because we worked in a complicated environment in a bank, if I say it was difficult, you will think the tool was complex, which isn't the case. But if I claim it was easy, it wasn't.

I would rate the initial setup a three out of five.

Our organization achieved the ROI.

Pricing is one of those situations where the more you use it, the more you pay. However, the cost is variable. And, if used properly, I believe it is rather inexpensive. If you use it badly, you must pay.

If one is very cheap, and five is very expensive, I would rate the pricing a two out of five.

We had many others and did a replacement. We decided on Elastic Observability because it was the most cost-effective.

My recommendation is to start small and gradually expand. Don't attempt to implement or distribute over a vast estate all at once. Begin small. 

Use Agile methodology. Basically, don't go large at first. Take a little bit and then grow.

I would rate Elastic Observability an eight out of ten.

We use it to handle significant volumes of data sourced from various network monitoring protocols like NetFlow and SNMP.

We're capable of monitoring fleet-based applications as well as custom applications effectively. This capability provides us with robust performance insights, enabling us to pinpoint and address issues with precision.

The ability to ensure that the data is searchable and maintainable is highly valuable for our purposes.

The interface could be improved. Currently, the aspect that impresses me the most is the AI functionality. However, the pricing for the AI-powered APM feature is quite steep.

I have been using it for two years.

We are satisfied with the stability, as we never faced any issue with it.

The scalability is excellent, and we're quite satisfied with it. It's quite straightforward for us.

The technical support is actually very good. We haven't encountered any issues with it because our engineers are proficient with Elastic.

We initially experimented with a couple of other systems before settling on Elastic. I can't recall the specific alternatives we explored. After conducting an initial Proof of Concept, we proceeded to production with Elastic, and we're currently satisfied with it.

The initial setup is straightforward.

We have been using the open-source version.

If compared with Splunk, which is known for its high cost, Elastic is freely available as open-source software. I prefer Elastic because of its affordability. However, I acknowledge that Splunk is also a robust platform, albeit at a significant expense.

I would recommend it. Overall, I would rate it seven out of ten.

It offers end-to-end observability, the capability of monitoring and analyzing the entire stack, from the user experience to the low-level infrastructure. It enables troubleshooting and debugging by allowing us to trace issues through the entire system.

It is a powerful tool that allows users to collect and transform logs as needed, enabling flexible visualization and analysis.

Improving code insight related to infrastructure and network, particularly focusing on aspects such as firewalls, switches, routers, and testing would be beneficial.

I have used this solution for three years.

While there have been some stability issues, they are not considered major problems. I would rate it seven out of ten.

In terms of performance and scalability, it provides high efficiency and reliability. It can manage data without any issues with its scalability capabilities. I would rate it eight out of ten.

They provide a really good support. I would rate it eight out of ten.

Positive

Based on previous experience, Dynatrace has been considered practical with good features, but its usage depends on the specific environment. On the other hand, Elastic is versatile and can be tested in any environment to determine its value. It can be configured according to the desired specifications.

The initial setup was complex. It involved significant administration and the implementing team faced many challenges.

The implementation and deployment process took about six months to complete.

Elastic Observability is cheaper than other similar solutions, such as Dynatrace. Its license calculation is based on various factors like data volume and physical infrastructure, particularly related to RAM capacity. It may also vary in different countries.

When considering technology, it is important to focus on its capabilities rather than viewing it solely as a tool. It requires to be constantly learning and adapting to different configurations. I would rate it seven out of ten.

We are using Elastic Observability for monitoring.

The solution has been stable in our usage.

Elastic Observability is difficult to use. There are only three options for customization but this can be difficult for our use case. We do not have other options to choose the metrics shown, such as CPU or memory usage. 

I have been using Elastic Observability for approximately two years.

I rate the stability of Elastic Observability a ten out of ten.

We have approximately 10 people using the solution in my organization.

We use the solution daily.

I have not used the support from the vendor.

I have not used another similar solution to Elastic Observability.

We have a lot of Kubernetes clusters making the initial setup more difficult. If we only had one cluster of Kubernetes it would be simple. We have to do a lot of the setup manually. 

If someone had a simple environment the setup could be easier but it depends on the environment.

I rate the initial setup of Elastic Observability a five out of ten.

The price of Elastic Observability is expensive.

I rate the price of Elastic Observability an eight out of ten.

I rate Elastic Observability an eight out of ten.

The architecture and system's stability are simple. The storage management behind the massive platform and the service speed are good.

There could be on-site support services available in the Middle Eastern region. Also, more web features could be added to the product.

I have been using Elastic Observability as a distributor for one and a half years.

The product is stable. There are a few occasional issues with the platform's stability.

The product's scalability is good.

I worked with LogRhythm and Rapid7 before. Elastic provides better security, comparitiviely.

The initial setup process is simple. Working on the dashboard is easy. For small to medium businesses, it can take up to 15 days; for medium to large businesses, it can take 30 days.

Elastic Observability's pricing could be better for small-scale users. It is very competitive and good for large-scale users. The node for the end user might cost around 16k. We'll allow them to implement all the modules Elastic can provide, from EDR to integration with the NDR. All of these features will take full advantage of the node. If we need to enable any other feature, we need a professional service from the experts.

I rate Elastic Observability a nine out of ten.

We use it for monitoring the application performance and development.

We use AppDynamics and Elastic. The reason why we're using Elastic APM is because of the license count. It's very favorable compared to AppDynamics. It's inexpensive; it's economical.

The auto-discovery isn't nearly as good. That's a big portion of it. When you drop the agent onto the JVM and you're trying to figure things out, having to go through and manually do all that is cumbersome. 

We just started using it in the last month.

It is stable. We didn't find any issues.

You could scale it nicely. Currently, we have 400 or so app devs who are using it.

I have used their tech support, and they've been great. I'd give them a 10 out of 10.

We were using New Relic.

It's more complex. AppDynamics does a lot more auto-discovery in the setup.

You're not going to get around not having to do the work.

I would rate Elastic APM a seven out of 10.

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.