Solid multi-ingestion tool but with poor exception handlingThe major pain point with Zaloni is that their exception handling is not good. If any event happens (an event is when the job stops in the middle of the process), it doesn't tell you at which point it failed and it doesn't tell the operations team how they should take corrective actions unless you call Zaloni and then identify the issues. That is one issue. Another issue is that sometimes your jobs fail and if you run it a second time, it will go through. A third area it could be improved is the deployment process. When you want to deploy anything, it has a lot of manual processes. For example, you have to create your password in an encrypted format, and then you have to use a lot of manual deployment process. They should actually be building something else, like using Jenkins or automating their process. I have suggested to them that they have to improve their deployment process because they want everyone to run a manual deployment. It takes a lot of time, about half a day, for any single deployment. Then test it, then it might not work, and then reverting back is not easy because of the manual deployment process. I think in recent versions they added a lot of upgrades and additional features including a lot of integrations. Before it was just AWS, later they extended it to Azure. I'm not sure how they have extended it to GCP. It has some built-in features and a lot of improvements now because the UI and the features were not easy to navigate. Regarding showing the metrics, it's okay. I will say it's neither easy nor hard, there is whatever is required. Lastly, on the governance side, it's not very good. We faced some issues with the Ranger version. Ranger was an authentication tool on big data and Zaloni had some compatibility issues with the Ranger at that time. Later they said those are all going to be resolved, but at that time it had some issues. I'm not sure whether it was working with the Sentry or not.
