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.
I would rate the product an eight out of ten. The tool is only for logs and dashboards. However, it is not recommended for cross-logging and resource monitoring.
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.
Logz.io is great. For any other project we create it will be one of the staple products where I will say, "We should just start with this upfront, as opposed to trying to find another solution later or reassessing it, because there is no reason not to start with the product right now." Then, we will find its niche for whatever it is we are making in the future. I think this solution is super useful. It is a common go-to for a lot of the team who use it. We use the solution’s AI-powered Insights feature, but not as heavily as maybe we should. It is definitely interesting to see what is going on and what the AI-powered Insights are telling us is going on. That can be really useful. We don't necessarily look at AI-powered Insights for troubleshooting and root cause. We are looking at it more to tell us something it thinks is going on. I will look at Insights maybe once a week, and say, "Oh, I get it. This is interesting. This is a new thing that seems to be happening. Let's have a look, see if we can dig down, and determine why it is coming up with that insight." If we see a lot of problems, then we go and look at Insights first. Normally, we are too busy trying to diagnose problems to think about Insights. While it is a good feature, we probably don't lean on it enough. I would rate this solution as a solid nine out of 10.
Production Engineer at a healthcare company with 51-200 employees
Real User
2021-04-18T17:13:00Z
Apr 18, 2021
The implementation and usage are good once you figure them out but sometimes the beginning can be hard. Once you get it, it's okay. We have 10 developers who are working with logs and we have two developers who are developing all the infrastructure around logs. We have about 10 people who are using their Kibana product.
AWS Technology Lead at a tech services company with 1,001-5,000 employees
Real User
2021-04-12T19:58:00Z
Apr 12, 2021
Make the best use of the support services Logz.io provides. The customer concierge is there to make sure that you are onboarded correctly. Your customer success manager and technical point of contact are very helpful. They will really speed up your implementation on your configuration. Make best use of the people that they make available to you. Logz.io is being used every day by the team on a customer project. They log in everyday to look at logs and dashboards as well as search logs. This is a really important part of the toolkit that we provide to our customer through our teams. I would rate Logz.io as a nine out of 10.
Logz.io is a 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 four products: Log Management built on ELK, Infrastructure Monitoring based on Prometheus, Distributed Tracing based on Jaeger, and an ELK-based Cloud SIEM. These are offered as fully managed, integrated cloud services designed to help engineers monitor, troubleshoot and secure their...
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.
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.
I would rate the product an eight out of ten. The tool is only for logs and dashboards. However, it is not recommended for cross-logging and resource monitoring.
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.
I would rate the product a nine out of ten.
Logz.io is great. For any other project we create it will be one of the staple products where I will say, "We should just start with this upfront, as opposed to trying to find another solution later or reassessing it, because there is no reason not to start with the product right now." Then, we will find its niche for whatever it is we are making in the future. I think this solution is super useful. It is a common go-to for a lot of the team who use it. We use the solution’s AI-powered Insights feature, but not as heavily as maybe we should. It is definitely interesting to see what is going on and what the AI-powered Insights are telling us is going on. That can be really useful. We don't necessarily look at AI-powered Insights for troubleshooting and root cause. We are looking at it more to tell us something it thinks is going on. I will look at Insights maybe once a week, and say, "Oh, I get it. This is interesting. This is a new thing that seems to be happening. Let's have a look, see if we can dig down, and determine why it is coming up with that insight." If we see a lot of problems, then we go and look at Insights first. Normally, we are too busy trying to diagnose problems to think about Insights. While it is a good feature, we probably don't lean on it enough. I would rate this solution as a solid nine out of 10.
The implementation and usage are good once you figure them out but sometimes the beginning can be hard. Once you get it, it's okay. We have 10 developers who are working with logs and we have two developers who are developing all the infrastructure around logs. We have about 10 people who are using their Kibana product.
Make the best use of the support services Logz.io provides. The customer concierge is there to make sure that you are onboarded correctly. Your customer success manager and technical point of contact are very helpful. They will really speed up your implementation on your configuration. Make best use of the people that they make available to you. Logz.io is being used every day by the team on a customer project. They log in everyday to look at logs and dashboards as well as search logs. This is a really important part of the toolkit that we provide to our customer through our teams. I would rate Logz.io as a nine out of 10.