Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Great tool all around
What do you like best about the product?
I love the querying ability -- it is very robust and allows a lot of flexibility
What do you dislike about the product?
I really do not have any dislikes... sometimes it takes a while to query but that's it
What problems is the product solving and how is that benefiting you?
Finding errors in the logs to pinpoint issues as they are happening in real-time -- fewer errors in production
Recommendations to others considering the product:
Very useful for checking on your logs and ensuring that everything is functioning as expected.
- Leave a Comment |
- Mark review as helpful
Good message granularity, but difficult to write queries.
What do you like best about the product?
I love how in depth the query results are. Being able to filter a certain log field is very useful, and something I had not seen before in older version of Kibana. Being able to drag a specific time range in the log visualization tool and have the logs for that time range pop up are very useful. The JSON field formatting is also extremely useful. We use this to trace through logs and have been able to determine the flow of any particular request in our services. This has saved significant amounts of time as opposed to having to trace through entire log entries.
What do you dislike about the product?
I find myself constantly having to relearn how to write more complex queries. For anything simple, things are usually straightforward, but I find myself having to rely on saved queries too often for anything even moderately complex.
What problems is the product solving and how is that benefiting you?
Being able to filter logs by type in production are very useful, seeing JSON fields formatted is a huge boon.
Recommendations to others considering the product:
Use saved queries lots, it is easy to forget how to write complete queries from scratch. And make sure to format logs correctly in order to take advantage of JSON field filtering that sumo offers. The system is daunting at first, especially when compared to simpler systems like Kibana, but honestly it is significantly more powerful and robust.
good option for managed log ingestion and analysis
What do you like best about the product?
I like their flexible approach to parse fields out of log entries, kind of like linux pipes, to allow you concatenate multiple extraction rules, and aggregate options
What do you dislike about the product?
I've only scratched surface, but for our fairly low volume operation, the price tier is a little steep. I wish they could provide more tiers for light users, then ramp up when needs arise
What problems is the product solving and how is that benefiting you?
As we are a tiny team, we don't want to build and keep up with our own log ingestion and analysis platform. But our log structure is fairly diverse, so the analysis part has to be very flexible. Sumo Logic fits the bill and let us save precious dev time.
Living in SumoLogic
What do you like best about the product?
My team handles internal support for our employees and we're constantly shifting through logs to determine what our employees and online customers are doing within our application. It's fun playing detective!
What do you dislike about the product?
There's definitely a learning curve for finding the right information and making sure it's ported correctly.
What problems is the product solving and how is that benefiting you?
We've weeded out so many workflow issues and discovered bugs in my short time at TRR.
Recommendations to others considering the product:
It's a fantastic tool for any technical/dev ops, product, or CS team to determine at a granular level how users are operating on your site but you can also zoom out to see larger trends. Useful on so many levels.
Power of sumo Logic
What do you like best about the product?
Best tool especially when we deal with unstructured data.
Great platform for auditing our applications.
easy to learn.
not much complications.
Great platform for auditing our applications.
easy to learn.
not much complications.
What do you dislike about the product?
It can have a client version instead of web browser.
Certain important usecases are hard to find in Google and sumo logic help page.
Certain important usecases are hard to find in Google and sumo logic help page.
What problems is the product solving and how is that benefiting you?
Our applications run on AWS now. I am trying to create dashboards for my support teams to ease their maintenance and higher management for their audit review.
Consolidated Logs simplify near real time monitoring
What do you like best about the product?
Sumo logic is a flexible product which simplifies log searches and lends itself to fast, scalable implementations. Making the most of Sumo takes time, but there's a lot to take advantage of.
What do you dislike about the product?
The command sets for advanced functionality are not always intuitive.
What problems is the product solving and how is that benefiting you?
Primarily we are using Sumologic to supplement our existing alerting methodologies by performing log scans simultaneously across all relevant products with a single, simple query, rather than implementing those log scans via application or cron. The simplicity and speed that their log consolidation offers is an enormous time saver.
Recommendations to others considering the product:
Direct collection is much better than using forwarders; web hooks can and should be configured, identify key logs and collect them to keep costs down rather than trying to collect everything under the sun.
Flexibility, rapid iteration
What do you like best about the product?
Sumologic provides flexibility to dump logs from our existing log modules and get the data directly to sumologic. We can have data in tags etc.
What do you dislike about the product?
Not much to say here. There are no bugs we report. Only issue is related to how large data you dump.
What problems is the product solving and how is that benefiting you?
debugging errors and alerts based on what we have
Flexible Log Analytics Power Tool
What do you like best about the product?
Time to market:
- Because Sumologic is a SAAS product, I don't need to run an ELK stack or manage any logging / storage infrastructure.
- Because Sumologic is a supported product, I have full access to a team of engineers who wrote the software and to customer success engineers to help leverage the all the features and debug mistakes
- Because Sumologic stores the raw logs, I can always refine and clean up the data in ad-hoc queries over historical data
- Because of the flexible query language, I can iterate on a data pipeline in minutes instead of hours or days (I'm looking at you DataFlow)
Taken as a whole, these features make it possible to quickly build out and iterate on complex log data.
Because Sumologic holds the raw logs (not just metrics), its always possible to clean the data in a way that would not be possible using only
- Because Sumologic is a SAAS product, I don't need to run an ELK stack or manage any logging / storage infrastructure.
- Because Sumologic is a supported product, I have full access to a team of engineers who wrote the software and to customer success engineers to help leverage the all the features and debug mistakes
- Because Sumologic stores the raw logs, I can always refine and clean up the data in ad-hoc queries over historical data
- Because of the flexible query language, I can iterate on a data pipeline in minutes instead of hours or days (I'm looking at you DataFlow)
Taken as a whole, these features make it possible to quickly build out and iterate on complex log data.
Because Sumologic holds the raw logs (not just metrics), its always possible to clean the data in a way that would not be possible using only
What do you dislike about the product?
- Enriching the data is somewhat hard
- Under load the UI is not as responsive as I would like
- Exporting the enriched data is somewhat hard
- For my use case, its very difficult to make reusable portions of queries that are shared by many searches / dashboard panels
- The tradeoff with log analysis tools like Sumo and others versus metric-based data is that complex queries take more time. This isn't a Sumologic problem, its just the downside of the flexibility that comes with log in general
- For large scale projects , care must be taken to stay within the various limits -- though compared to other tools like OpenTSDB Sumologic is much less limited
- Under load the UI is not as responsive as I would like
- Exporting the enriched data is somewhat hard
- For my use case, its very difficult to make reusable portions of queries that are shared by many searches / dashboard panels
- The tradeoff with log analysis tools like Sumo and others versus metric-based data is that complex queries take more time. This isn't a Sumologic problem, its just the downside of the flexibility that comes with log in general
- For large scale projects , care must be taken to stay within the various limits -- though compared to other tools like OpenTSDB Sumologic is much less limited
What problems is the product solving and how is that benefiting you?
Overall business objective: Detection and understand root causes of problems with network traffic for online video.
Benefits:
- Faster time to market
- Reduced maintenance
- Customer support
- Domain expertise
- Fast Iteration
Benefits:
- Faster time to market
- Reduced maintenance
- Customer support
- Domain expertise
- Fast Iteration
Recommendations to others considering the product:
Think about total cost of ownership before choosing either an open source product (like OpenTSDB, ELK, Graylog, or InfluxDB). In particular, estimate:
* Capacity Planning -- what load will monitoring analytics solution need to handle at peak? Do you have staff with experience scaling out that platform to that scale? Are the scaling characteristics of this product at that scale well understood?
* Data ingest costs in your preferred cloud / on-premise hosting solution and how much infrastructure you'll need to ingest that data.
* Support Contracts -- How much will a support contract cost to help you get unstuck quickly?
* Time to build out an MVP -- will you need to manage lots of infrastructure yourself? Can you leverage an in-house operational team that will immediately prioritize your project above other work? (In many cases, in house teams are already over-committed in my experience)
* Familiarity with the Data -- if you already understand the data well (from working with it in a different product for example), you may not need the flexibility of Sumologic
* Cycle Time - How long will it take to make a single small change to your MVP? Minutes or days? Whats your dead line to having an acceptable version in production?
In short, if you are cash rich and time poor but need to iterate and scale rapidly, look at a SAAS offering like Splunk, Sumologic, or Elastic. In many cases, Sumologic will actually win on price over the offerings and for me, I've seen Sumologic perform well at high scale.
If you are time rich and cash poor or already understand your dataset / problem domain well AND you don't expect to scale out your system significant in the next 2 to 5 years, you might be able to save money by oeprating an open source product in house. However, you will almost certain pay with your development and maintenance time.
* Capacity Planning -- what load will monitoring analytics solution need to handle at peak? Do you have staff with experience scaling out that platform to that scale? Are the scaling characteristics of this product at that scale well understood?
* Data ingest costs in your preferred cloud / on-premise hosting solution and how much infrastructure you'll need to ingest that data.
* Support Contracts -- How much will a support contract cost to help you get unstuck quickly?
* Time to build out an MVP -- will you need to manage lots of infrastructure yourself? Can you leverage an in-house operational team that will immediately prioritize your project above other work? (In many cases, in house teams are already over-committed in my experience)
* Familiarity with the Data -- if you already understand the data well (from working with it in a different product for example), you may not need the flexibility of Sumologic
* Cycle Time - How long will it take to make a single small change to your MVP? Minutes or days? Whats your dead line to having an acceptable version in production?
In short, if you are cash rich and time poor but need to iterate and scale rapidly, look at a SAAS offering like Splunk, Sumologic, or Elastic. In many cases, Sumologic will actually win on price over the offerings and for me, I've seen Sumologic perform well at high scale.
If you are time rich and cash poor or already understand your dataset / problem domain well AND you don't expect to scale out your system significant in the next 2 to 5 years, you might be able to save money by oeprating an open source product in house. However, you will almost certain pay with your development and maintenance time.
Power log aggregation and analysis tool
What do you like best about the product?
I like being able to easily search and correlate data across all our various log files. The query functionality is quite advanced compared to what is available when grepping log files at the command line.
What do you dislike about the product?
It's never going to be as performant as searching fully structured/indexed data. We also have had issues bumping up against our ingress limitations (we have a lot of logs).
What problems is the product solving and how is that benefiting you?
We use sumologic to do investigation during production outages as well as longer-term analysis during product launches (performance monitoring, etc). Using logs to drive dashboards can be challenging to set up but once you do, you not only have a nice high-level dashboard, you can dig in to the low-level details that you're putting into your logs.
Data collection and analysis
What do you like best about the product?
The team behind the product. This support and engineering teams were very helpful and used there knowledge of product to build out some useful dashboards
What do you dislike about the product?
live mode reliability. Often live mode would not stay in continuous mode and i would have to refresh the page to get updated information. I also noticed that there were login issues a few times over the course of a 6 month trial 100% uptime is key to having a successful producct
What problems is the product solving and how is that benefiting you?
real time analysis of the cdn and component involved in our pipelines. We did have to rely on other systems at time due to delays but setting up and not having to admin the infrastructure was helpful.
Recommendations to others considering the product:
I would recommend working with vendors services as there is often issues related to search api and dashboard issues that could not be resolved on user side.
showing 221 - 230