Hi, it will not work for two reasons:
- Warp 10 is expecting a POST request on the exec endpoint with a WarpScript as raw body (ie: [ <your token> 'my.series' {} NOW 1 h ] FETCH ->JSON ) and do not pass the token as an auth mode. You could use the Fetch endpoint (ie: '
https://warp.instance/api/v0/fetch?token=<your read token>&selector=~.*\{\}&now=now×pan=-1') with a GET request but you miss all the analytics power of WarpScript.
- and the blocking part:
https://rdc.codezero.xyz/#/rest-explorer awaits for "Content-Type: application/json" as an HTTP header in the response, but Warp 10 does not provide this header (at least in the current version, maybe in a further release). This Web connector crashes when this header is missing (you can contact the developer to fix it:
https://github.com/niranjan94/rest-data-connector/issues).
But, (there is a good news :) ), like the blog post said, there is a workaround : use the HTTP Plugin to deploy a custom macro (which add the missing header). You could contact the OVH-Metrics team to deploy the Warp 10 HTTP plugin and the dedicated macro.
Best regards,