Does any one know any convertor for Prometheus Query Language to Kusto Query Language? Thanks
Both systems work quite differently, so as far as I have researched yet, there is no 100% conversion from one to the other. (I’d be glad to be proved wrong here)
Prometheus has a row with corresponding values, so you can do things like http_server_requests_seconds_sum/http_server_requests_seconds_count to get the average time requests needed in the time bucket of the data row. That is easy, because you have all metrics “in hand”.
In Kusto resp. Azure Minitoring each value of a prometheus endpoint scrape is saved as dedicated row. So to do the calculation which is easy in promql, you have to somehow join the table with itself, find the correct row that corresponds by the timecode and other labels (in case of multiple instances, you’d need to match them too), then you can do the calculation.
I have not yet calculated that successfully and we are thinking of switching to self hosted prometheus in the light of these huge differences.