
I use Oodle AI mainly for ingesting logs from my software stack and querying them to monitor system health and handle issues. It works seamlessly with our AI tools like Claude code and Cursor, making integration easy and cost-effective. What I like most is the ease of integration with Claude code, as I don't need to learn another query language; I can explain what I need in natural language and let Oodle AI handle the rest. Setting up infrastructure through Claude is smooth, like setting up dashboards or configuring metrics for visualizations. Review collected by and hosted on G2.com.
The UI itself can feel very sluggish at certain points, and the UX is a bit inconsistent in some places. For example, I often find that while configuring filters for a query, the query starts before I really intended, and there's no way for me to stop the query until it's done. It can also slow down when viewing a broad query over a wide time range. An explicit play/stop button when running queries would be helpful. Also, there are improvements needed to the log pipeline - for example, there's no obvious way in the UI to edit the execution order of steps in the pipeline. Review collected by and hosted on G2.com.
Hey Aneesh, great to see the sunshine and rainbows that Oodle brings to your Claudy days! We ourselves use the English-to-PromQL heavily, and love it, awesome to see you do too.
๐ So many goodies for you over the last month:
Logs UI now lets you stop and cancel an in-flight query. Log-pipeline steps can now be re-ordered with drag-and-drop in the UI. We have put in multiple performance improvements in the logs UI, making it snappier, do give it a whirl :)