Logz.io Reviews

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 query mechanism for response codes and application health is valuable. It can predetermine if we have a problem or if the error count goes up. It is our standard logging solution. It egressed out our various networks, whether PCI or non-PCI, consistently. 

The product provided us with a consistent logging platform. Our engineers and app owners are really educated on it. Even though we’re the product owner, the app teams often use it for performance problems like service times and consistency of application health.

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

The product needs improvement from a filtering perspective. 

The tool helped us to aggregate logs for several microservices and make dashboards to help us to monitor the application. 

Aggregating events happening simultaneously among several microservices, since we can aggregate the logs into a single repository of data

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.

Lockdown and COVID-19 made it impossible to go to work anymore. Having a central place where everybody could have a login, then we could share, take snapshots of graphs, or send people live data. Then, if anybody wants to know, they can just go and have a look for themselves. They don't have to ask us, "What is the state of the services like?" or, "What does the player population look like?" We don't have to answer those questions. People can just go and find the answers by looking at it themselves. Also, the customization means we can very quickly build graphs to analyze data or check something out. If somebody else wants something else that isn't there, then it is a very quick turnaround to add it very quickly.

Logz.io is useful for helping us to correlate between our log, metrics, and tracing data. They are integrated altogether, so we have our observability metrics dashboard with a link in there. You click it, then it goes to the logs. It is a holistic approach to having everything together. 

It has definitely improved our troubleshooting: To have visibility on what is going on so we can identify things as early as possible. The alerting system is super powerful and hooked up to all our systems so we get alerts. Whenever there is an inkling of a problem, we know about it. That is just incredibly useful rather than having to wait for someone to tell us, which is theoretically what the old world used to be like: Someone would have to notice. Now, we can build alerts in it and the solution will tell us. 

For anyone who uses it, Logz.io has increased their productivity. There is no restrictive policy on who can go and find out some basic information or look at graphs. Our design team, customer service team, engineering team, and executive team can all look at it from different levels. They can just go to the dashboard or graph where they want to see the information, without having to ask anybody. This adds a layer of transparency and demystifies a lot of stuff going on, which helps productivity for the sheer fact that anyone can see it. There is a lot of data in Logz.io to be consumed, but it is very clearly laid out and not confusing.

The solution was used for log management. 

InsightOne is the main reason why we use LogMeIn. This is mostly because of log data that we are pushing tools and logs in general. 

We use the product for log collection and monitoring. 

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

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.

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.

Our team doesn't spend time setting up, managing, and tuning a logging platform. It frees them up to spend time on higher value pieces of work. A customer is getting a much higher value for their money. It allows our people to focus on the high-value business change work. Before, we would have been managing that on a daily basis and that would have taken up a certain percentage of the team's time. These platforms aren't exactly easy to manage and can be quite complex, especially when it comes to the scale.