Logz.io Reviews and Ratings

Use Cases and Deployment Scope

I use it regularly to monitor our application logs. Mostly use to check our user's issue with the help of visualization and dashboard Alert triggering really useful to monitor our live data and take the necessary steps to avoid the issue in future customer support also really good

Likelihood to Recommend

Logs monitoring Visualizing Alerts for frequent errors and warning in application

Use Cases and Deployment Scope

Logz.io is an awesome tool for analyzing logs of our servers, the UI and UX are very cool and very convenient to understand, and their customer support is very good, they are so kind and fast, overall this tool is a good tool

Likelihood to Recommend

it is well good in the log management, but quit down in other features

Use Cases and Deployment Scope

We use Logz.io as a log aggregator, to bring together all the logs from different cloud services, and as a log explorer and analyzer as once the logs are in the same place it is much easier to review logs, find and investigate problems, and improve the logging of the products.

Likelihood to Recommend

It is very helpful when having logs distributed in different products, cloud services, etc; and/or you don't have a tool/way to explore them.

It is not that helpful if your solution already has all the logs in the same place and you have a way to explore them already.

Use Cases and Deployment Scope

We use it as a log management and log centralize collector. We pipe all our cloud application and SaaS platform activity and event logs to logz.io for audit and compliance purpose. Logz.io meet the needs and requirements for logs management for ISO 27001 audit and security risk & compliance.

Likelihood to Recommend

We use it as a log management and log centralize collector. We pipe all our cloud application and SaaS platform activity and event logs to logz.io for audit and compliance purpose.

Logs are stored in logz.io for investigation and audit purposes. However not all cloud platform is able to pipe their logs over.

Use Cases and Deployment Scope

We currently use Logz.io as our primary logging tool for our applications. This is managed by the engineering department. Our primary use case for these logs is troubleshooting and monitoring of errors our production and test environments.

Likelihood to Recommend

Logz.io is an effective solution if your alerting needs are fairly straightforward and you don't need long-term retention of logs with easy access. If being able to maintain easy access to logs longer than this is necessary, another solution might be better. If you need a high degree of precision with alerting triggers and the ability to suppress alerts, you will need to combine Logz.io with an integration to get this or you might consider a different solution.

Use Cases and Deployment Scope

Logoz.io is used in my company since the end of last year and we are using this tool for monitoring of our infrastructure, cloud and end user application. It's now being used by my engineering department and we are planning to use the security solutions on our networking section. We are currently running a huge infrastructure on the cloud as well as in our premises to get user analytics and in order to ease the log management we are using the Logoz.io solution. It's a great tool to manage the log data on both the cloud and application. We are looking forward to exploring more solutions that fit our needs from Logz.io.

Likelihood to Recommend

Logz.io is well suited for infrastructure management and application monitoring. Our major issue is with the application management and issue tracking which can be done easily in Logz.io. Also the DevOps analytics tool is well managed in terms of ease of use. Our team is now relying mainly on the data analytics and monitoring tool on the application and on the cloud to get work done.

Use Cases and Deployment Scope

We use Logz.io in the application development department because it works automatically to resolve any failure in the codes of the same, which allows us to have an infrastructure with great support and availability, and helps us focus on improving our applications and leave this great monitoring works to Logz.io. In this way, we are sure that if a failure occurs we will be able to notice instantly and be able to solve it immediately.

Likelihood to Recommend

<div>It is appropriate for companies that focus on developing extremely simple applications. The great visibility it provides makes it ideal to avoid problems that may affect the entire business or company thanks to the fact that it is capable of emitting dozens of alerts in a short time. Sometimes the search behavior becomes slow and inefficient, which can be uncomfortable.</div><div>

</div>

Use Cases and Deployment Scope

We use logz.io for centralized logging from all production servers. We analyze the data collected by logz.io to fix problems proactively and troubleshoot real-time issues.

Likelihood to Recommend

Anytime you want to run ELK stack or want just want centralized logging, logz.io is an affordable tool that is far better than anything else I have ever seen. It’s a lot cheaper than splunk, and cheaper/less maintenance than elastic cloud.

Use Cases and Deployment Scope

It is being used throughout our development stack to consolidate logs. We utilize microservices and push all our logs to logz.io.

Likelihood to Recommend

It is well suited for grabbing logs from distributed microservices and combining them into one place. It isn't ideal for throwing random junk that is unstructured into it.