Logz.io

Software just works making it very quick to get up and running to see insights in your data. The team is adding features on a regular basis, adding value to the product. Integration with third-party systems is also great - we use PagerDuty and Slack integration.

Dashboards are a great feature where we configure our important metrics to see at a glance how things are going - also makes it easy to on-board technical personnel as you can show them how all aspects of the application are working (as long as you are capturing the correct metrics).

The ability to share a specific view with a client is a great feature - let's your customer see what is happening with their specific services / apps.

Limitations on sub-account numbers - this is an artificial limit - make data volumes the one factor around costings.

Fast, familiar Kibana interface, quite good filter selection/manipulation GUI, good alerts and sharing functionality.

The Insights functionality is of no value - whatever it finds/suggests is never related to any real issue we have. Filter value lists are based on 500 messages only and often selection of less frequent values (usually the more interesting ones) requires going into Visualize screen. Ad hoc parsing of messages and extraction of values (a la Loggly) is missing. Missing ability to set all filters in GUI before the query is actually performed (suspended update). Some little bugs with refresh when filters are changed.

Easy to filter things, add and remove extra filters.
Nice visualization of log results

The query language is not the one you're use to.
Building dashboards is not intuitive.

All logging information is passed to logz IO, is easily searchable, filterable and easy to format to our organisations needs. Also slack integration is pretty easy.
Search is fast and takes a seconds at worst, less than a second a most times.
After IDE this is the tool i used the most.

Sometimes the search doesn't behave as expected. for instance search for a string triggers too much information, and there is a need to filter by fields first and than do the search.
Also would help when searching for exception, if the tool can highlight the code base specific lines in stack flow, but it's easily searchable.

Logz.io provides a familiar interface for anyone using ELK. It scales to meed our demand, even on our busiest days. I'd need to hire a team to maintain an infrastructure this size.

Search UI has unique behavior that requires a small amount of familiarization. The use of spaces and special characters adds complexity.