
Logz.io Open 360 Observability Platform (Subscription)
Centralized logs have improved troubleshooting and now reduce production incident impact
What is our primary use case?
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.
How has it helped my organization?
Logz.io has impacted our organization very positively. It has improved our visibility across our systems and cloud resources, and it has reduced the effort of finding the root cause. It has also reduced manual effort of troubleshooting and helped us to identify issues before they impacted customers.
We have experienced approximately 40 to 50% reduction in troubleshooting time and it has fastened the process of incident response during production outages.
What is most valuable?
The best features of Logz.io are the centralized log aggregation, fast search and filtering capabilities, and their support for OpenTelemetry. Their dashboards and visualization are very good.
The main feature is the centralized log management, which has the biggest impact in our organization. Having logs from all the services and infrastructure in one place reduces our troubleshooting time and also improves incident response.
Logz.io is particularly useful because it scales well as environments grow. Adding new services and applications is very straightforward compared to maintaining self-hosted logging solutions.
What needs improvement?
Logz.io can be improved by adding more AI-assisted root cause analysis and by improving log retention flexibility. They can also provide additional dashboard customization options.
Logz.io is a very mature and grown platform with very good features. Most improvements should be around automation, AI-driven insights, and cost visibility.
Because Logz.io is a very mature and grown platform that is very good, cost optimization can be made for higher costs related to higher log volumes. For larger organizations, custom dashboards can be improved. In terms of root cause analysis, there can be more AI-assisted root cause analysis capabilities.
For how long have I used the solution?
We have been using Logz.io for more than one year.
What do I think about the stability of the solution?
We have found that Logz.io is reliable and available for our operational needs.
What do I think about the scalability of the solution?
Logz.io handles the growing log volumes and additional services very well without requiring major architectural changes from our side.
How are customer service and support?
Customer support is very good. The team is very responsive and knowledgeable whenever we need their assistance.
Which solution did I use previously and why did I switch?
We previously relied on self-managed ELK and also used CloudWatch Logs for some workloads. Managing and scaling a self-hosted logging platform requires significant operational effort. We wanted to switch to a managed solution with better observability capabilities and reduce our maintenance overhead.
How was the initial setup?
The setup process is straightforward. Pricing is competitive compared to building and maintaining a self-hosted observability stack, especially when factoring in operational effort.
What about the implementation team?
We directly procured Logz.io through their company.
What was our ROI?
The biggest ROI comes from the reduced troubleshooting effort, less time spent managing logging infrastructure, and faster issue resolution. It has also improved our system's reliability.
What's my experience with pricing, setup cost, and licensing?
Organizations that start with clear logging standards and retention policies can integrate applications, cloud resources, and Kubernetes workloads early to maximize the observability benefits. They can monitor log ingestion costs as their environment grows.
Which other solutions did I evaluate?
Before Logz.io, we also evaluated DataDog, Sumo Logic, and New Relic platforms.
What other advice do I have?
Our review rating for Logz.io is 8 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
An amazing hosted Grafana service
Finding the needle in a haystack...
logzio - one stop solution
A very useful and versatile logging system
Many integrations are supported out of the box. We use it daily.
logzio - one solution for all observability needs
kubernetes specific monitoring and alerting
siem and traces support
ability to breakdown costs per kubernetes namespace
Logz.io - decent logging system
Searchability is good
Clear and concise expandable logs
I use it infrequently compared to other tools, but is a smooth integration and onboarding experience.
Powerful platform for log management and analytics
Seamless integration with various tools like kibana and grafana
User friendly dashboard
Complexity in advanced configurations like setting up custom parsing rules