Error when enable instrument in TYK API gateway

I got this error when enable instrument in TYK API gateway.
(Instrumentation)

level=warning msg=“application connect failure” error=“Post https://collector.newrelic.com/agent_listener/invoke_raw_method?license_key=&marshal_format=json&method=preconnect&protocol_version=17: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)” prefix=newrelic

Connection testing result :

HI @thsurachai

Thanks for reaching out here, I hope you are well.

Also congrats on your first post here.

This is a little out of my scope of knowledge, but we see you and we are here to help. I will loop in an API Engineer here to have a look.

Please note they will reach out here with any updates they may have. Should you have an update or additional questions, please do reach out!

It looks like you are actually getting a 400 Bad Request response. It’s connecting to the collector but it is rejecting the request. It could be due to a bad license key. Please validate the INGEST - LICENSE key.

@dkoyano License key is correct one. I’m not sure that another request body param might be required.
(actually method is POST but the response is same)

license was captured from tyk configuration here:
image
image

Hello @Surachai.Thanaprasit,

Thank you for the extra information regarding this, it really helps. Our support engineers are looking over this and will get a response out shortly. We appreciate your patience.

You might need to check with TYK for this. This is what their forums say.

The 400 (Bad Request) status code indicates that the server cannot or will not process the request because the received syntax is invalid, nonsensical, or exceeds some limitation on what the server is willing to process. It means that the request itself has somehow incorrect or corrupted and the server couldn’t understand it. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method . Therefore, it prevents the website from being properly displayed. The main thing to understand is that the 400 Bad Request error is a client-side error.

The cause of a 400 error can be a wrongly written URL or a URL that contains unrecognizable characters. Another cause of the error might be an invalid or expired cookie. Also, if you try to upload a file that’s too large. If the server is programmed with a file size limit, then you might encounter a 400 error.

1 Like