Logz.io Reviews

We have a product that our customers are using on their servers, and we stream all the logs from our services that are on those servers to Logz.io. We do analysis of the logs and we also have alerts if we don't have enough logs or if a certain log is not arriving and then we know that there's a problem with the server.

The infrastructure is comfortable to use and work with and Logz.io has helped us in managing our logs better and improving our logging system.

The visualizations in Kibana are the most valuable feature. It's much more convenient to have a visualization of logs. We can see status really clearly and very fast, with just a couple of clicks.

The solution’s Drop Filters are currently helping us filter out logs that we're not sure whether we want to eliminate completely or not. The solution is great because it gives us a middle ground where we don't have to decide right away if we want to stop streaming the logs or hold onto them longer. That helps drive cost-efficiency when logging within Logz.io.

We're mainly doing correlations either within Kibana or within the metrics, and that is also helping us.

When it comes to reducing our troubleshooting time, it depends. When there are no bugs in Logz.io, it reduces troubleshooting by 5 to 10 percent. When there are bugs, it increases our troubleshooting time by 200 percent or more.

Also, the API could be more stable.

I've been using Logz.io for a year.

In the past year we've had four major incidents, so I would say the stability is average.

The support could be more reachable and help more when it comes to bugs. I don't get assistance from their support when I approach. I would rate them at five out of 10.

The availability of the customer success personnel from Logz.io who work with our company is amazing, but when it comes to the tech support tech, while the first response is fast, the rest of the conversation can take a while, and then I have to check with them about what is going on because I don't get information.

It took a couple of weeks to implement the solution in our company.

The implementation and usage are good once you figure them out but sometimes the beginning can be hard. Once you get it, it's okay.

We have 10 developers who are working with logs and we have two developers who are developing all the infrastructure around logs. We have about 10 people who are using their Kibana product.

The tool helped us to make logs and dashboards for microservices. It also helped us to monitor the application. 

The tool is simple to setup where it is just plug and play. The tool is reliable and we never had any performance issues. 

The solution needs to improve its data retention. It should be greater than seven days. The product needs to improve its documentation as well. 

I have been working with the product for six to eight months. 

We have never experienced any bugs or instability issues.

The solution is scalable. Our engineering team uses the product which can be around 70 people. 

We didn't have any problems and hence haven't contacted the support yet. 

The product's pricing is cheaper than other solutions. 

I would rate the product an eight out of ten. The tool is only for logs and dashboards. However, it is not recommended for cross-logging and resource monitoring. 

We use the tool to track the dev and production environment. 

The product needs improvement from a filtering perspective. 

I have been using the product for a year. 

The product was stable until we reached a certain limit which was around 10-20 GB. 

My company had 50 users for the product. We had used three to four microservices and we didn't experience any lag. 

The product's setup is straightforward if you know the documentation. A senior developer helped us with the tool's setup. We had integrated the old framework and hence had to go through the documentation. 

I would rate the product a seven out of ten. The product's setup is pretty cool and easy. From the developer's perspective, the logs are good. There is plenty of documentation available on how to use it and check logs.  

We use the product for log collection and monitoring. 

The solution needs to expand its access control and make it accessible through API. 

I am using the tool for thirteen months.

The product is stable. 

We had lost log events during workloads. My company has around 500-1000 users for the product. 

The support team is responsive. 

The tool is an open source product. 

I would rate the product a nine out of ten.