My pusher does not support custom HTTP headers
Update content

My pusher does not support custom HTTP headers

Reviewed on 03 April 2023Published on 03 April 2023
Security & Identity (IAM):

You may need certain IAM permissions to carry out some actions described on this page. This means:

  • you are the Owner of the Scaleway Organization in which the actions will be carried out, or
  • you are an IAM user of the Organization, with a policy granting you the necessary permission sets

If your pusher does not support the X-Token header, there are other ways to pass it:

  • Through the X-Scope-OrgID header. This means that when using Promtail, you can set the tenant_id field of the client’s configuration to pass the token.
  • Through the Authorization: Bearer <token> header. This is for all clients who usually have support for these bearer tokens.
  • Through the Authorization: Basic header. With basic authentication you will have to use the token as a password with any username.

If none of these methods were successful, reach out to us on the #observability-beta channel on slack.