Logz.io Open 360 Observability Platform (Subscription)

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 can query a lot of data points and build dashboards. The vendor is good at adjusting their models. Most companies want us to forecast our yearly use and pay it upfront on day one. 

With Logz.io, we commit to use 14 TB in a year. However, they measure us every month and give us a monthly bill. Depending on our monthly usage, we pay for 14 TB divided by 12 months or a little extra. It's a little bit more like AWS. Other solutions do not do it. They want their money upfront.

We really like the dashboards. We have 36 sub-accounts. Each sub-account is an app, and we could put restrictions on that app. Previously, there were capacity restrictions on the sub-accounts. 

If we have a sub-account of 1 TB and use only 100 GB, we waste 900 GB that day. We could not share it between sub-accounts. Now, they provide an overhead volume. We do a reserve, and any sub-account could use anything over the reserve. It utilizes our footprint better.

Capacity planning could be a little bit of a struggle. The product must add some AI capabilities to learn from previous behaviors. Instead of us setting thresholds, the tool should learn the thresholds, notice when we are out of the normal thresholds, and fix it.

I have been using the solution for four to five years. We are using the latest version of the solution.

I rate the tool’s stability an eight out of ten. There have been some times when queuing has occurred. For example, when we send a message, it takes a certain amount of time for it to pop up on the dashboard. It doesn't happen very often, but they notify us.

I rate the tool’s scalability an eight out of ten.

The support is great. We meet weekly.

Positive

We used Dynatrace. Now, Dynatrace has a competitive log solution. If we have our application monitoring and logging on one tool, it would give us stronger visibility. It is a potential option for us.

The initial deployment was pretty straightforward. The hardest part was figuring out how to egress and working with every development team to change the logging endpoints. We used F5 before. Since it is a SaaS solution, the vendor does all the upgrades and enhancements.

We have seen a return on investment. It has provided us with proactive monitoring. We could have had many outages that would have cost us hundreds and thousands of dollars an outage.

The product is a little expensive. We're pushing 17 TB. It costs us one and a half million dollars a year.

People who want to use the product must work on their financials and go a little thin on particular apps. They must educate the app teams and empower them to use the query capabilities. Overall, I rate the tool an eight out of ten.

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. 

The price can be cheaper and they should have better monitoring. 

I have been using Logz.io for two years. 

It is a stable solution. 

It is a scalable solution. 

We did not contact the technical support team because we followed the documentation. 

We used to use New Relic for marketing as well, for example for infrastructure marketing. Later on, we decided to push logs only to New Relic. A the time, we wanted a single marketing tool like New Relic.

The initial setup is easy. They have some documentation and it does not take much time. We only implement. The model marketing model, the dashboard, and all those things are already in the application. You could create different dashboards and filter as needed.

If the marketing log is available, then it is a very good product in general. 

I rate the overall solution a nine out of ten. 

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

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, but this may be a contract issue. The product needs to improve its documentation as well, since it is vage in some parts.

I have been working with the product for six to eight months. (Year: 2022)

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 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.