INGESTION_API_KEY doesn't work with hyperdx-all-in-one docker image
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
HTTP status code 401. Error message: scheme or token does not match
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the 401 response with INGESTION_API_KEY configured in the hyperdx-all-in-one Docker image, then trace the ingestion authentication path to find where the scheme or token is rejected. Done means the configured key is accepted and ingestion succeeds, with a regression test or documented verification for the image configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- authentication, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100