feat(evlog): add edgeUrl ingest support#110
Conversation
|
@gabrielelpidio is attempting to deploy a commit to the HRCD Projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Thank you for following the naming conventions! 🙏 |
afe9ef9 to
4e7a464
Compare
|
@gabrielelpidio Thanks for the PR! Quick question, when edgeUrl has a custom path (e.g. https://edge.axiom.co/custom/ingest/), the dataset is not appended, only the trailing slash is stripped. Is that intentional? If so, could you document this behavior? The config table currently only mentions "Uses /v1/ingest/{dataset}" without this exception. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
Hey! Yes, it's intended, added some documentation around it |
🔗 Linked issue
Resolves #46
Fixes EVL-47
📚 Description
This PR adds edge endpoint support to the Axiom adapter and aligns evlog’s config surface with the Axiom SDK direction.
Changes included:
edgeUrlsupport increateAxiomDrain()config resolution.NUXT_AXIOM_EDGE_URLAXIOM_EDGE_URLedgeUrlxorbaseUrl) for adapter and Nuxt module options.edgeUrl->/v1/ingest/{dataset}baseUrl(or default) ->/v1/datasets/{dataset}/ingestedgeUrlpaths as-is (trim trailing slash), matching upstream behavior.edgeUrl.Validation run locally:
bun run test test/adapters/axiom.test.tsbun run build(package)bun run lint src/adapters/axiom.ts src/nuxt/module.ts test/adapters/axiom.test.ts📝 Checklist