External reviews
External reviews are not included in the AWS star rating for the product.
Tools that makes the search quciker
- Leave a Comment |
- Mark review as helpful
Modern platform for observability and application performance monitoring
Most of the tasks in Elastic Enterprise are automated, i.e. creating a cluster is just a matter of few clicks.
An end user can login to the UI using their email address and perform fast searches on the past documents and other relavant data.
Review on Elastic Enterprise Search
If you want a Unified Data Platform. "Elastic Search"
BI, APM, Searching, Security, SIEM. All these solutions can be used on one platform.
In order to use all of these solutions, you have to review and purchase each solution individually, but Elastic search can build them all on one platform at a low price.
I was cross-examining whether to change the H/W or the configuration to improve performance and increase speed, and one of them was elastic search.
We confirmed the maximum result at the minimum cost, and obtained the result of rapid performance improvement and the desired target value.
Great tool that just works
Critical tool for central logging
Best elastic searching tool
Migrate from ELK to Grafana
Once you have defined your query and fields, you can choose the one you want from a defined widget list and.. you will have a working widget.
ELK has been a solid product in the market for a long time, so the bugs in the search mechanism may minor
(I didn't find a bug )
In Log4J situation, ELK reacts fast and sends us a report with all clusters that possibly have this vulnerability and suggest a plan.
Support is also good.
It's answering fast, willing to help, and there is a vast community and documentation for everything.
So when you face an issue, be sure someone else has met with the same problem before, and he will probably publish an answer for your case.
It's costly to have ELK cluster, even for the most minor needs.
Maintenance:
We always need to take care of the number of shards, do maintenance and increase the cluster even if we have free space.
I took time for us, more than usual EC2 maintenance.
We used ELK and Kibana for that.
Then, each Client got their dashboard link and user management mechanism.
A difficult company to work with
The CloudFormation template seems to have a slight bug in it when you try to use it outside of us-east-1. That or there is an alternative bucket name beside the default I should be using. It was easy to work around in main stack, but the stack references templates for sub-stacks in an S3 bucket. I'm sure I could have grabbed the contents of the bucket, made my own bucket, made my own templates, and made it all work, but it bugged me to bill a client for time spent doing all of this to make a SaaS solution, which should save us time, work.
I've explained the issue to Elastic seven times in the last week. I even included snips of their problematic template, highlighted the offending lines, and suggested how they might fix the issue. But they won't help themselves or me. Instead, they seem terrified that I'm going to get free support out of them, and the free support has taken days to demonstrate that they don't know what I am saying. I still could have worked around this, but I fear it foreshadows what future interaction might be like if I did get cornered by an issue.
Two stars vs. one, because I've used the product under Docker Compose. Elastic Stack has issues, but it is generally an exciting and powerful product. I don't want to be stuck working with a company that acts this way and I believe that it is primarily the managed service they are offering that I am reviewing.
Billing and "Trial" version
I wanted to check this product - choosing the trial version was a huge mistake. As now Elastic trying to take my money, despite the fact that I never used the product. At all. And no communication from the support or any billing support at all.
Why am I getting charged for the service I have never been able to use?