CloudWatch has the worst UX of any log management tool I've used. We are using Logentries currently, and it is so easy and intuitive.
I just don't get how AWS developers are able to accept the eyesore that is their UX. It's easy to miss things in any AWS service's UI. I keep discovering functionality even after years of use. Google Cloud UX is light years ahead. Also, Google's Stackdriver seems great, haven't used it yet though. Would be great if any Stackdriver users here share how it is better than CloudWatch or other log management tools.
I just tried it. It's just as bad as AWS UI ever has been. It shows lots of fields that it extracted from the log messages. Can you click them to add them to the search box? Nope. Right click for more options? Nope. These are things Splunk has had for years.
Teams are under control of their backlog in a way that let's them prioritise how they approach the UX/UI aspects. For instance, this is why you'll see 2-3 different UIs across AWS journeys, due to teams implementing at different paces and priorities.
Comments
CloudWatch has the worst UX of any log management tool I've used. We are using Logentries currently, and it is so easy and intuitive.
I just don't get how AWS developers are able to accept the eyesore that is their UX. It's easy to miss things in any AWS service's UI. I keep discovering functionality even after years of use. Google Cloud UX is light years ahead. Also, Google's Stackdriver seems great, haven't used it yet though. Would be great if any Stackdriver users here share how it is better than CloudWatch or other log management tools.
Have you tried Insights?
I just tried it. It's just as bad as AWS UI ever has been. It shows lots of fields that it extracted from the log messages. Can you click them to add them to the search box? Nope. Right click for more options? Nope. These are things Splunk has had for years.
Why is this though? Is Amazon not employing UX/designers? Is there a culture there that trivializes UX benefits?
Teams are under control of their backlog in a way that let's them prioritise how they approach the UX/UI aspects. For instance, this is why you'll see 2-3 different UIs across AWS journeys, due to teams implementing at different paces and priorities.
I use Logentries currently, and frankly using "grep" on my logs is often faster than extracting what I need from Logentries.
Yeah, it's slow, I'll give you that. But for now we can live with that. We are a 4 member shop, it's a problem for another day :).