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
2021-04-18T17:13:00Z
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
2021-04-12T19:58:00Z
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 is a leading cloud-native observability platform that enables engineers to use the best open source tools in the market without the complexity of operating, managing, and scaling them. Logz.io offers four products: Log Management built on ELK, Infrastructure Monitoring based on Prometheus, Distributed Tracing based on Jaeger, and an ELK-based Cloud SIEM. These are offered as fully managed, integrated cloud services designed to help engineers monitor, troubleshoot and secure their...
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.