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.

One of those areas would be allowing it to have public dashboards where you don't need a login. The reason is if we were in a studio right now, we would have a big screen TV with the dashboards on it. That would mean someone would have to log into it. Right now, it is not a problem. However, in the future, this will be. We will want these dashboards on big TVs so we can just visually see the state of the world. You have to log in right now to see anything. Whereas, it would be nice if we could have a link to a dashboard that we could give to anybody without having to log in. That way, we can put it into a kiosk. So, we could put it into a kiosk mode, then just have graphs on a big screen all the time without having to log in. That is a feature that would be great to have and a feature that I have asked for a couple of times.

I would like granularity on alerting so we can get tentative alerts and major alerts, then break it down between the two, but they do have a lot of good alerting stuff in there already.

The product needs improvement from a filtering perspective. 

I would like them to improve how they manage releases. Some of our integrations integrate specifically with set versions. Logz.io occasionally releases an update that might break that integration. On one occasion, we found out a little bit too late, then we had to roll it back. In those rare situations, the customer team were all over it. They helped us get back online again. They should enable customers to manage updates themselves, e.g., give my team the choice whether we want to upgrade and when. That way, we can manage it a little bit more effectively on our side. This is the only thing where they could improve. This is based on an experience a year ago, so my information might be a little bit out of date.

The solution needs to expand its access control and make it accessible through API. 

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

The solution needs to improve its data retention. It should be greater than seven days. The product needs to improve its documentation as well. 

When it comes to reducing our troubleshooting time, it depends. When there are no bugs in Logz.io, it reduces troubleshooting by 5 to 10 percent. When there are bugs, it increases our troubleshooting time by 200 percent or more.

Also, the API could be more stable.