Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
342 reviews
from
External reviews are not included in the AWS star rating for the product.
Sumo logic satisfait mes besoins.
Qu'aimez-vous le plus à propos de the product?
La chose que je préfère chez Sumologic est l'interface utilisateur. Créer, enregistrer et partager de nouvelles requêtes est très simple.
Que n’aimez-vous pas à propos de the product?
Je n'aime pas la lenteur avec laquelle Sumologic se remplit de messages. Cependant, je ne suis pas sûr si c'est dû au fait qu'ils sont d'abord écrits dans CloudWatch avant que Sumo ne les récupère. Dans le passé, nous utilisions Kibana et les journaux apparaissaient immédiatement.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Vue complète du système de tous les messages de journal de nos services avec une filtration facile
Rapide et facile moyen d'accéder aux journaux
Qu'aimez-vous le plus à propos de the product?
La meilleure partie concerne l'accès et le filtrage des journaux avec des requêtes.
Que n’aimez-vous pas à propos de the product?
Je ne pense pas, d'après mes souvenirs, que Sumo Logic fonctionne bien avec des éléments qui ne génèrent pas un 'standard' de journal. Je souhaite qu'il y ait plus de personnalisation pour les tableaux de bord.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Surveillance des erreurs, Suivi des erreurs
Super outil dans l'ensemble
Qu'aimez-vous le plus à propos de the product?
J'aime la capacité de requête -- elle est très robuste et permet beaucoup de flexibilité.
Que n’aimez-vous pas à propos de the product?
Je n'ai vraiment pas de dégoûts... parfois cela prend du temps pour interroger mais c'est tout.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Trouver des erreurs dans les journaux pour identifier les problèmes au fur et à mesure qu'ils se produisent en temps réel -- moins d'erreurs en production
Recommandations à d’autres personnes envisageant the product:
Très utile pour vérifier vos journaux et s'assurer que tout fonctionne comme prévu.
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.
bonne option pour l'ingestion et l'analyse de journaux gérés
Qu'aimez-vous le plus à propos de the product?
J'aime leur approche flexible pour extraire des champs à partir des entrées de journal, un peu comme les pipes Linux, pour vous permettre de concaténer plusieurs règles d'extraction et des options d'agrégation.
Que n’aimez-vous pas à propos de the product?
J'ai seulement effleuré la surface, mais pour notre opération à volume assez faible, le niveau de prix est un peu élevé. J'aimerais qu'ils puissent offrir plus de niveaux pour les utilisateurs légers, puis augmenter lorsque les besoins se font sentir.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Comme nous sommes une petite équipe, nous ne voulons pas construire et maintenir notre propre plateforme d'ingestion et d'analyse de journaux. Mais notre structure de journaux est assez diversifiée, donc la partie analyse doit être très flexible. Sumo Logic répond à nos besoins et nous permet d'économiser un temps de développement précieux.
Vivre dans SumoLogic
Qu'aimez-vous le plus à propos de the product?
Mon équipe gère le support interne pour nos employés et nous passons constamment en revue les journaux pour déterminer ce que nos employés et nos clients en ligne font au sein de notre application. C'est amusant de jouer au détective !
Que n’aimez-vous pas à propos de the product?
Il y a certainement une courbe d'apprentissage pour trouver les bonnes informations et s'assurer qu'elles sont transférées correctement.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Nous avons éliminé tant de problèmes de flux de travail et découvert des bogues pendant mon court séjour chez TRR.
Recommandations à d’autres personnes envisageant the product:
C'est un outil fantastique pour toute équipe technique/dev ops, produit ou CS pour déterminer à un niveau granulaire comment les utilisateurs opèrent sur votre site, mais vous pouvez également prendre du recul pour voir des tendances plus larges. Utile à de nombreux niveaux.
Puissance de Sumo Logic
Qu'aimez-vous le plus à propos de the product?
Meilleur outil, surtout lorsque nous traitons des données non structurées.
Excellente plateforme pour l'audit de nos applications.
Facile à apprendre.
Pas beaucoup de complications.
Excellente plateforme pour l'audit de nos applications.
Facile à apprendre.
Pas beaucoup de complications.
Que n’aimez-vous pas à propos de the product?
Il peut avoir une version client au lieu d'un navigateur web. Certains cas d'utilisation importants sont difficiles à trouver sur Google et la page d'aide de Sumo Logic.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Nos applications fonctionnent désormais sur AWS. J'essaie de créer des tableaux de bord pour mes équipes de support afin de faciliter leur maintenance et la direction pour leur examen d'audit.
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.
Flexibilité, itération rapide
Qu'aimez-vous le plus à propos de the product?
Sumologic offre la flexibilité de déverser des journaux à partir de nos modules de journaux existants et d'obtenir les données directement dans Sumologic. Nous pouvons avoir des données dans des balises, etc.
Que n’aimez-vous pas à propos de the product?
Pas grand-chose à dire ici. Il n'y a pas de bugs que nous signalons. Le seul problème est lié à la quantité de données que vous déversez.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
les erreurs de débogage et les alertes basées sur ce que nous avons
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.
showing 261 - 270