-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Gravitee.io API Gateway #83
Comments
Hi @brasseld thanks for reaching out and happy to hear that you want to add Gravitee.io as a new traffic source. We definitely need to add a new doc describing how people can add more traffic sources, for now I can point you to the plugins API (go client code is already generated here). There is also a section in the helm values to enable each traffic source with a specific values for each one. |
Thanks for your feedback @FrimIdan It's probably me doing something wrong (or maybe I missed something) but when I try to Postman for creating (post) a new telemetry, I'm always getting a 400 response:
What I'm trying to POST to /api/telemetry:
(This has been mainly generated by Postman by importing the swagger you provided me). Thanks for your feedback. |
Ok, seems that the error message is quite clear body.body has to be base64 encoded (would be great to update the swagger to add a description about it :) ) Now fighting with a 500 status code from clarity... |
Got it from logs, only base64 of json payload is supported :) |
format: 'byte' is not clear enough I agree - we didn't though about it since the generated client is handling that. |
Hi there,
I'm looking for contributing to provide integration between Gravitee.io API Gateway and API Clarity as a POC.
Do you have any pointer for me to start with? I had a quick look to the plugins you are providing for Kong and Tyk, but I didn't find any relevant information (API ?) where to push instrumentation metrics.
Thanks in advance.
The text was updated successfully, but these errors were encountered: