Elastic Agent
ElasticReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
23 reviews
from
External reviews are not included in the AWS star rating for the product.
Logstash Review
What do you like best about the product?
It logs the activities from all the servers and aggregates them into one source of truth for visualization and researching.
What do you dislike about the product?
The logs take a while to understand for non-technical person at the beginning
What problems is the product solving and how is that benefiting you?
To keep logs and be able to track back to see what activities were performed by what users
Versatile log processor with ample community support and rapid updates
What do you like best about the product?
The thing I like the most about logstash is the ability to adjust it to whatever you are doing. If it is your own custom project, or a standard input source it will bend to your needs.
What do you dislike about the product?
Setting up logstash took a while when I had no idea how to get it working. What I am trying to say is the learning curve was a little higher than I thought. That and GROK is horrible.
What problems is the product solving and how is that benefiting you?
Analyzing windows and Linux log files for common use, and miss use of computers. Being able to see in one central location how all of the systems and clients are behaving is wonderful.
Recommendations to others considering the product:
Learn to use Grok. Find a Grok parser online and then look for a LOT of guides on how to write grok. There are plenty of them out there.
When you have found your guide, test out your code. Set up a CI / CD environment, even if it is a simple one to test out your changes to your logstash configuration files.
Make sure you setup all your inputs and outputs as separate files, it makes for a LOT easier debugs.
Use a version control system like git, it makes finding problems with your configuration changes a LOT easier
Basically what I am saying is follow the principals of DevOps, logstash is trouble
When you have found your guide, test out your code. Set up a CI / CD environment, even if it is a simple one to test out your changes to your logstash configuration files.
Make sure you setup all your inputs and outputs as separate files, it makes for a LOT easier debugs.
Use a version control system like git, it makes finding problems with your configuration changes a LOT easier
Basically what I am saying is follow the principals of DevOps, logstash is trouble
Good open source software
What do you like best about the product?
Very good performance when processing and collecting logs big in size.
Open source with a big community and a lot of plugins available.
Open source with a big community and a lot of plugins available.
What do you dislike about the product?
High memory consumption.
Somewhat hard to setup.
Somewhat hard to setup.
What problems is the product solving and how is that benefiting you?
We needed a way to easily find recurring build system problems that are in our hundreds of logs.
With the implementation of elk(elastisearch, logstash, kibana) we can now easily search all of our logs at once.
With the implementation of elk(elastisearch, logstash, kibana) we can now easily search all of our logs at once.
showing 21 - 23