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.
External reviews
62 reviews
from
and
External reviews are not included in the AWS star rating for the product.
The solution is a consistent logging platform that provides excellent query mechanisms
What is our primary use case?
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using the solution for four to five years. We are using the latest version of the solution.
What do I think about the stability 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.
What do I think about the scalability of the solution?
I rate the tool’s scalability an eight out of ten.
How are customer service and support?
The support is great. We meet weekly.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
The product is a little expensive. We're pushing 17 TB. It costs us one and a half million dollars a year.
What other advice do I have?
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.
A stable solution that inventories all of your data and provides a single place to filter out any data
What is our primary use case?
The solution was used for log management.
What is most valuable?
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.
What needs improvement?
The price can be cheaper and they should have better monitoring.
For how long have I used the solution?
I have been using Logz.io for two years.
What do I think about the stability of the solution?
It is a stable solution.
What do I think about the scalability of the solution?
It is a scalable solution.
How are customer service and support?
We did not contact the technical support team because we followed the documentation.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What other advice do I have?
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.
A reliable tool for logs and dashboards
What is our primary use case?
The tool helped us to aggregate logs for several microservices and make dashboards to help us to monitor the application.
How has it helped my organization?
Aggregating events happening simultaneously among several microservices, since we can aggregate the logs into a single repository of data
What is most valuable?
The tool is simple to setup where it is just plug and play. The tool is reliable and we never had any performance issues.
What needs improvement?
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.
For how long have I used the solution?
I have been working with the product for six to eight months. (Year: 2022)
What do I think about the stability of the solution?
We have never experienced any bugs or instability issues.
What do I think about the scalability of the solution?
The solution is scalable. Our engineering team uses the product which can be around 70 people.
How are customer service and support?
We didn't have any problems and hence haven't contacted the support yet.
What's my experience with pricing, setup cost, and licensing?
The product's pricing is cheaper than other solutions.
What other advice do I have?
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.
Helps to track the dev environment
What is our primary use case?
We use the tool to track the dev and production environment.
What needs improvement?
The product needs improvement from a filtering perspective.
For how long have I used the solution?
I have been using the product for a year.
What do I think about the stability of the solution?
The product was stable until we reached a certain limit which was around 10-20 GB.
What do I think about the scalability of the solution?
My company had 50 users for the product. We had used three to four microservices and we didn't experience any lag.
How was the initial setup?
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.
What other advice do I have?
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.
A stable solution for log collection and monitoring
What is our primary use case?
We use the product for log collection and monitoring.
What needs improvement?
The solution needs to expand its access control and make it accessible through API.
For how long have I used the solution?
I am using the tool for thirteen months.
What do I think about the stability of the solution?
The product is stable.
What do I think about the scalability of the solution?
We had lost log events during workloads. My company has around 500-1000 users for the product.
How are customer service and support?
The support team is responsive.
What's my experience with pricing, setup cost, and licensing?
The tool is an open source product.
What other advice do I have?
I would rate the product a nine out of ten.
Which deployment model are you using for this solution?
On-premises
Very good sulotion to complicate problem
What do you like best about the product?
The product's Usability is greate. You can find what you need easily and performance is also ok even in big queries
What do you dislike about the product?
Insights tab should be improved.
Improve performance is always nice
Improve performance is always nice
What problems is the product solving and how is that benefiting you?
Investigating bugs on customers' servers
Get alerts that helps me to find issues before customer does
Get alerts that helps me to find issues before customer does
Recommendations to others considering the product:
Go for it. Will solve you many problems
Head of Service Reliability
What do you like best about the product?
The combination of ElastichSearch, Kibana and Alerts make production monitoring easy since you can quickly send log, visualize and create alerts to get notified when something happened. The setup is pretty simple and the support team is very quick to answer, since they have a chat tool.
What do you dislike about the product?
We faced an issue while ago where some information we were sending were not being properly parsed/stored in elastic search, as a consequence an exception was being raised, and stored as a normal message. Due that problem we reached our daily storage quota because the exception message as really big. I think in this cases would be better to not store anything.
What problems is the product solving and how is that benefiting you?
Monitoring production environments are easy with this solution
A must-have for the DevOps team
What do you like best about the product?
Customized alerts to ensure production is safe
Efficiency of the GUI to identify a problem
Efficiency of the GUI to identify a problem
What do you dislike about the product?
The system of quotas can act as a brake. Sometimes, a problematic client sends too many logs, the quota is reached, and we lose future logs for the day. We have fixed that by implementing a throttle in the log picker.
What problems is the product solving and how is that benefiting you?
A regular example is about payment methods. Many apps are involved. To find where the problem is, we have to find logs in many apps over a long period to understand the use case.
Logz.io simply works
What do you like best about the product?
Works fast and smooth.
The support team provides excellent service.
The support team provides excellent service.
What do you dislike about the product?
Minor features are absent from ELK stack
What problems is the product solving and how is that benefiting you?
Using a single query (for example, a customers' ID) across multiple indices, indexes and multi-millions of logs is extremely helpful and works really fast. This gives you the ability to look for a single value across domains (analytics, application, infrastructure, etc.) and get a better view of the problem origin.
Recommendations to others considering the product:
Logz.io is a SAAS company that's actually run by people.
They are very open, have good advice and excellent customer support.
They are very open, have good advice and excellent customer support.
Best support
What do you like best about the product?
Logz io is great tool for analyzing logs.
I guess there are many tools like logz.io but the special thing is the support.
Any time I had an issue, even when I needed help with regex expressions the support chat helped me with understanding, patience and very fast.
I guess there are many tools like logz.io but the special thing is the support.
Any time I had an issue, even when I needed help with regex expressions the support chat helped me with understanding, patience and very fast.
What do you dislike about the product?
I wish saving data wasn't part of the payment agreement and logzio would keep my data for more than 30 day. But business is a business
What problems is the product solving and how is that benefiting you?
I'm using logz.io for:
live tail to follow my actions.
Analyzing logs.
Sending alert using the alert tool
live tail to follow my actions.
Analyzing logs.
Sending alert using the alert tool
showing 1 - 10