We have been using Logz.io for more than one year. Our main use case for Logz.io is centralized log management and observability. We collect logs from multiple applications and infrastructure components, which allows our team to troubleshoot issues quickly. A recent example involved an API that failed in our production environment. We have multiple Java services running and communicating with each other, and users were reporting transaction failures. Using Logz.io, we had all the logs centralized, so our developers quickly identified the database connection pool issue and fixed it without delay. This helped in finding the root cause very significantly. Beyond troubleshooting, we also use Logz.io for proactive monitoring, alerting, and security investigation. It has become one of our primary tools that our operation teams rely on daily.
Senior Manager of Operations at a comms service provider with 10,001+ employees
Real User
Dec 12, 2023
We have 1500 servers and 600 applications. They all use Logz.io. Most of our apps have a seven-day retention. We use the product for application health and security compliance. After seven days, it goes to the archive so we can recall if we somehow had a security incident. It’s our only logging solution.
Our primary use case is to monitor the live game observability. When our game is live, we can see how the servers are performing and how players are connecting around the world. Generally, we just monitor everything to make sure the stability is running smoothly. The secondary use of it is when we have things we want to dig deeper into, then we have a backup of the logging system. We can jump from a point in the metrics of the observability to a point in logging in which it happened, then observe what the server saw at that time in order to diagnose and fix whatever the issue might be.
Production Engineer at a healthcare company with 51-200 employees
Real User
Apr 18, 2021
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.
AWS Technology Lead at a tech services company with 1,001-5,000 employees
Real User
Apr 12, 2021
One of our customers uses it as a central logs aggregation point. We forward over logs from our customer environment in AWS to Logz.io. We use it to carry out dashboarding and analytics as well as for carrying out some alarming for certain scenarios and events. Essentially, it is a centralized log platform for a customer solution. We use Logz.io for cloud monitoring. I predominantly work in the cloud. That is all I have worked in over the last 10 years or so.
Logz.io provides a robust platform designed to streamline log monitoring, offering features like real-time dashboards and AI Insights. It ensures efficient management of environments such as Kubernetes, enhancing operational effectiveness and cost management.Logz.io is built on an open-source foundation, facilitating quick setup and adaptability for users. Its real-time dashboards are accessible across multiple sub-accounts, allowing seamless scaling and integration into existing services....
We have been using Logz.io for more than one year. Our main use case for Logz.io is centralized log management and observability. We collect logs from multiple applications and infrastructure components, which allows our team to troubleshoot issues quickly. A recent example involved an API that failed in our production environment. We have multiple Java services running and communicating with each other, and users were reporting transaction failures. Using Logz.io, we had all the logs centralized, so our developers quickly identified the database connection pool issue and fixed it without delay. This helped in finding the root cause very significantly. Beyond troubleshooting, we also use Logz.io for proactive monitoring, alerting, and security investigation. It has become one of our primary tools that our operation teams rely on daily.
We have 1500 servers and 600 applications. They all use Logz.io. Most of our apps have a seven-day retention. We use the product for application health and security compliance. After seven days, it goes to the archive so we can recall if we somehow had a security incident. It’s our only logging solution.
The solution was used for log management.
The tool helped us to make logs and dashboards for microservices. It also helped us to monitor the application.
We use the tool to track the dev and production environment.
We use the product for log collection and monitoring.
Our primary use case is to monitor the live game observability. When our game is live, we can see how the servers are performing and how players are connecting around the world. Generally, we just monitor everything to make sure the stability is running smoothly. The secondary use of it is when we have things we want to dig deeper into, then we have a backup of the logging system. We can jump from a point in the metrics of the observability to a point in logging in which it happened, then observe what the server saw at that time in order to diagnose and fix whatever the issue might be.
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.
One of our customers uses it as a central logs aggregation point. We forward over logs from our customer environment in AWS to Logz.io. We use it to carry out dashboarding and analytics as well as for carrying out some alarming for certain scenarios and events. Essentially, it is a centralized log platform for a customer solution. We use Logz.io for cloud monitoring. I predominantly work in the cloud. That is all I have worked in over the last 10 years or so.