---
title: "Comment by John Gordon on \"Enabling Chrome Extension Logging with Datadog: A Journey of Trial and Error\" | Hashnode"
description: "Just in case other people run into this: I was getting 403's when I implemented the solution in this blog. It turns out that my company uses a different datadog"
url: "https://hashnode.com/posts/enabling-chrome-extension-logging-with-datadog-a-journey-of-trial-and-error/64be67cbdff7801f7f82e1ae/comment/65bc09c0fba70baa45d0d678"
---

[Discussion](https://hashnode.com/posts/enabling-chrome-extension-logging-with-datadog-a-journey-of-trial-and-error/64be67cbdff7801f7f82e1ae)

Comment [Enabling Chrome Extension Logging with Datadog: A Journey of Trial and Error](https://hashnode.com/posts/enabling-chrome-extension-logging-with-datadog-a-journey-of-trial-and-error/64be67cbdff7801f7f82e1ae)

[John Gordon](https://hashnode.com/@jack589)

[Feb 1, 2024](https://hashnode.com/posts/enabling-chrome-extension-logging-with-datadog-a-journey-of-trial-and-error/64be67cbdff7801f7f82e1ae/comment/65bc09c0fba70baa45d0d678)

Just in case other people run into this:

I was getting 403's when I implemented the solution in this blog. It turns out that my company uses a different datadog enpoint than the default. So if you're using a different one, here's how to configure it:

```
const configuration = client.createConfiguration({
  authMethods: {
    apiKeyAuth: "pub...",
  },
});

configuration.setServerVariables({
  site: "us5.datadoghq.com"
});

const apiInstance = new v2.LogsApi(configuration);
```

[Aviv Elmakias](https://hashnode.com/@gripaviv)

[Mar 24, 2024](https://hashnode.com/posts/enabling-chrome-extension-logging-with-datadog-a-journey-of-trial-and-error/64be67cbdff7801f7f82e1ae/comment/65bc09c0fba70baa45d0d678#reply-65ffee515c8272e3f605f291)

Hi John, I would appreciate if you can elaborate on how did you find you have a different endpoint from the default.
