Do General HTTP Log Drains support arbitrary custom headers?

Support
1

Hi Netlify team,

We’re evaluating a SigNoz integration for Netlify Log Drains and wanted to confirm one technical point about General HTTP endpoints.

SigNoz Cloud requires the ingestion key to be sent using a custom header:

signoz-ingestion-key: <ingestion-key>

From the Netlify Log Drains docs, the General HTTP endpoint flow appears to support API key/query-param auth or the Authorization header:

Could you confirm whether General HTTP Log Drains support arbitrary custom headers?

If custom headers are not supported, is the recommended path for a provider like SigNoz to be added as a named Log Drain provider, or is there another supported auth pattern we should use?

Context:
We cannot use this URL-style setup with SigNoz:
https://signoz:<ingestion-key>@ingest.us.signoz.cloud:443/logs/json

Target pages:

Thanks,
Team SigNoz

2

Hi Netlify team, quick follow-up on this.

We’re still trying to confirm whether General HTTP Log Drains support arbitrary custom headers like signoz-ingestion-key.

If arbitrary custom headers are not supported, it would be helpful to know whether the recommended path is:

  1. using Authorization/query-param auth, or
  2. pursuing a named Log Drain provider integration for SigNoz.

This confirmation will help us decide whether the SigNoz + Netlify Log Drains docs path is feasible.

Thanks,
Team SigNoz