Hello @abdamou, thank you for feedback.
As a matter of fact, this morning @Dzuming took the time to add an extensive integration test suite dedicated to devtools alone. But yes, you are right we underestimated Devtools Kibana app and its apparent simplicity. It turned out having a few corner cases.
The initial bug: we always parse the body into JSON, which generated an empty object (even when dev tools request content-type wasn’t application/json). This caused
does not support having a body error.
POST _bulk kibana request body had
content-type application/json but carried invalid JSON (non-standard double quotes, for some reason) so when we tried to parse it, it causes a 400 bad request error.
We won’t try to parse the body of ANY dev tools console request, as we really don’t make use of it in ROR logic after all.
Maybe @Dzuming can confirm/correct me, but knowing his speed and typical work hours, I predict this fix will be delivered within the current day.
We will send you a pre-build ready to be installed.
By the way, please let us know if there are any other “hot spots” in Kibana functionality that are critical for your business case, and we should especially keep an eye on. We would be happy go beyond automated tests and go over those use cases manually.
Let me remark that as you are an enterprise customer, our support engineers, and myself are always at your disposal with top priority.