Comment by Sergiy Voznyak on "Enabling Chrome Extension Logging with Datadog: A Journey of Trial and Error" | Hashnode

Sergiy Voznyak

Nov 9, 2023

Hi Guy! Thank you very much for sharing your experience. Did you face a CORS error while sending logs to DD from the extension? I have a problem: all requests, either from background or content are rejected by Datadog with the error:

Access to fetch at 'http-intake.logs.datadoghq.eu/api/v2/logs' from origin 'chrome-extension://*********' has been blocked by CORS policy: Request header field dd-api-key is not allowed by Access-Control-Allow-Headers in preflight response.

Postman's exact (absolutely the same) request passed successfully (code 202 and entry in Datadog).

Guy Goldenberg

Senior Software Engineer @ Grip Security

Nov 28, 2023

Interesting! Generally, since the API should be accessible and must receive this header, I suspect this might be related to the endpoint you are trying to send the logs to.

I see that you are using http-intake.logs.datadoghq.eu/api/v2/logs

It's worth trying to send the requests to http-intake.logs.datadoghq.com/api/v2/logs (.com instead of .eu)

Let me know if it works :)

Hi. I'm facing a similar error as well. I think this behavior might be because the API is not designed to be called from a browser. I would be grateful if you could let me know if you find any workarounds.

Sargis

Jun 26, 2024

Guy Goldenberg

Unfortunately, I am also facing same issue. Works in postman, getting CORs issue from background script:

Access to fetch at 'http-intake.logs.us5.datadoghq.com/api/v2/logs' from origin 'chrome-extension://obdlkagmmgblbmgmflmkeopiennejpph' has been blocked by CORS policy: Request header field dd-api-key is not allowed by Access-Control-Allow-Headers in preflight response.

Search Hashnode