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.

A lot of people think you have to go with a company like Splunk if you want great server analytics. That couldn't be further from the truth. Logz is significantly less expensive and still has great features. That, plus the customer service, would lead me to recommend Logz to just about anyone.

I wear a lot of hats at work. People talk about how easy it is to set up an ELK stack, but it isn't when you've got so many other competing priorities. Logz made it easy to get ELK analytics up and running and has excellent added features such as machine learning to pick out additional issues. Logz is the gold standard for customer service among vendors I use. They've been incredibly patient and generous in helping me get the most of the product.

I understand why its newly-launched infrastructure monitoring product is based on Elasticsearch, but I'd rather it have been Prometheus-based.

query cross servers

Receive the query results quickly! Nice visuals.

we save only 14 days - which makes it less useful. Sometimes the search doesn't work as expected. The group by is very not intuitive.

Daily investigations of issues from logs are much easier with this tool.

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.

Can help detect and solve production issues

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.

Logz.io really helped ensure that our ELK stack was scaling to meet our needs. It took the guess work out of capacity planning as well.

I don't have to worry about scaling my ELK stack, those considerations are handled for us. Additionally the support is terrific, very responsive and the API documentation is outstanding.

Centralized logging solution that works. Its never down and allows me to do everything I need to do with logs.

It's just well done, and keeps getting better. Easy to find what I need and zooming in quickly to the root of the issue.

The query language is very strict could be simplified, but even that is a benefit because of compliance with ELK.

It takes aware the hassle of hosting your own ELK stack and dealing with scaling. The UI is nice and the API is really easy to use.

You will be paying a premium over hosting it yourself but the service is worth the money with the additions they provide and the customer support etc.

With Logzio we have had a great benefit in relation to the metrics that are generated through the logs collected from our servers. Through the generated graphs we can measure the efficiency of our services

Easy to use, intuitive tool helps us and is very useful in what we propose to do. We're reasonably satisfied

Do not support the Portuguese language of Brazil, this is a factor that we value greatly and could be improved.

Very good experience. Helpful team that are listening to customers

Includes a lot of easy-to-use features and provides a variety of levels for digging into logs, building dashboards

Implementation is a bit hard, especially the sub-accounts quota definition which required some adjustments

Proactive engineering team when it comes to production issues and customer support for our own service. Shortening root cause analysis of our own issues to the bare minimum. Applies a standard for observability in our own distributed system, helping new devs onboard quickly.

Customisation on top of kibana, alerts, dashboards. Simple integration to push logs to logz.io. Great support provided by logz.io!

Elasticsearch complexity requires some hand-holding, i.e. index failures. Some slowness in searches when the service is busy.

Affordable, simple to use, RBAC for internal users / staff viewing logs.

Setting up my logs to be sent to Logz was a breeze - we're using Docker, filebeat, and rsyslog. Literally it just works. The price is good and the support, the few times I've ever had to use it (for simple questions), has been great. Insights has caught so many bugs in my product that it's paid for itself.

Some things like SAML requires manual integration on the Logz side. This isn't usually a bad thing because it's a once off but I'd like to be able to do certain things without involving support.

Enables ingestion, indexing and search capabilities for all your logs in a big cloud-based application.

I am amazed about the ingestion and search capabilities. Integration with applications and specially with docker is a breeze.

Subscription plans should be more progressive, sometimes if the maximum event ingestion is met, the events are lost. Under those circumstances, the possibility to delete uninteresting events would help.

After having to setup ELK by ourselves, using it as a service is much more efficient albeit a bit expensive.

The ELK is fully featured and well documented. This way it is easy to find your way around. We also like the tokenized access we can give our customers.

Pricing : huge gap between 1GB/day and 5GB/day. Sometimes UI takes up to 10 seconds to load. Geo location data is old and inaccurate. Even after 4 or 5 requests it has not been improved.

clean interface and feature rich. timeless index, alerts actions supported by APIs, cloudtrail and account utilization

performance maybe poor depending on load of messages and query. Alerts should have multi query support and multi trigger support

Seems pretty straight forward.

The biggest features are how quickly you can gain access to your important data. Several times we have used logz.io to track down issues in real time with ease! In addition, if you have a suggestion or question, the response time is outstanding!

We can find any issues or bugs from Insights feature by just uploading the logs. Also we can store our data easily and cheaper on AWS S3.

This might be wish-to-have feature. If we could correlate the logs with IOCs like malicious URL or malicious IPs, it would be very happy.

Business information on customer trends in data, find common error messages and identify specific services that need improvement

Great for analysis of trends in log output, searching for that needle in a haystack, and triggering alerts

For developers, sometimes the interface feels like it gets in the way of the raw logfiles. Some overhead required to separate data into fields and identify numeric content for statistical charting. Occasional weird bugs in new features.

- No system administration - Nice user management - Data analyser - Power of elastic search - Very easy to use

The only cons i see is that Kibana is configured to only show the last 500 events on the web interface.

Finding production issues easily.

It has a powerful search mechanism on the logs. The UX is great (for example, I can add and remove a parameter to the search with a click).

I would like to get the raw logs around an exception that I found. Some minor UX issues that are not important.

Saves me time and money and it lets me reactive proactively to systems issues.

1) Saves me time 2) Great add-ons like AI to automagically analyze your logs 3)Alerts work well - we connect them to our pager duty account so we always know when something happens that needs our attention

It was easy to set up. The Logz.io specific features in the UI are very useful. The many different log shipping methods include great documentation.

Kibana can be overwhelming to new users. It does require some getting used to. This isn't really the fault of Logz.io though.

Insights feature help us find problem realtime! Until now out analyst took one hour and more to analyze multi logs. Logz.io help us reduce the cost!

The API document is too simple to integrate with our cloud system. If possible, please provide us more detail about API.

This is a much better solution that we had previously. It meets our PCI requirements, as well as all of our application requirements.

It is scalable and flexible. Support is magnificent. It meets every one of our needs, including SAML access controls. We love the integration with S3.