Logz.io is the 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 three products: Log Management compatible with ELK, Infrastructure Monitoring- a forked version created by Logz.io of the Grafana open source software, and an ELK-based Cloud SIEM. These are offered as fully managed, integrated cloud services designed to help engineers monitor, troubleshoot and secure their distributed cloud workloads more effectively. Engineering driven companies like Siemens, Turner Broadcasting, and Unity use Logz.io to simplify monitoring and security workflows, increasing developer productivity, reducing time to resolve issues, and ensuring the performance and security of their mission-critical applications.
Logz.io
Images
Check Software Images
Customer Reviews
Logz.io Reviews
Clay R.
Advanced user of Logz.ioWhat do you like best?
Logz.io provides a varity of different ways to ship your logs. They have log shipping options in the form of SDKs, log shipping daeoms, and cloud integrations, particularly with AWS. These optios are very robust and make it pretty easy to leverage Logz.io with your application. They documentation is also very helpful and does a good job clearing up any confusion or uncertainty. They've also release a limited Terraform provider for their platform which is super helpful if you are leveraging Terraform for any of your cloud resources. They support staff are top notch and get back to you very quickly. They have builtin parsers for many popular applications such as Nginx or MySQL which saves you the work of having to build a parser yourself.
What do you dislike?
While Logz.io has very competitive pricing, it required you to purchase average daily log volume. If you exceed that log volume for a 24 hour period, you are unable to ingest anymore logs for the remainder of that 24 hour period. I would much rather pay for log volume on a continous usage or just pay an addition amount for the excess log volume. I feel like most users wouldn't be happy with having a tempoarary loss of logging.
Recommendations to others considering the product:
I would check their documentation and see what SDKs and application integrations they provide. Changes are they provide a method for shipping logs that is compatiable with your current use case. They are pretty easy to get up and running with.
What problems are you solving with the product? What benefits have you realized?
I using Logz.io for application logging of a micro-service platform. It makes logging and monitoring containerized applications very easy. This has been vital for both rutine operations and for debugging during development activities.
