Conversation
Add a Send data guide for the Splunk HTTP Event Collector (HEC) compatible API served from the edge (hec.AXIOM_DOMAIN): the event, raw and health endpoints, the Splunk/Bearer/Basic auth schemes, index → dataset resolution, event-envelope field mapping, gzip payloads, and the Splunk response-code table. Link it from the send-data methods hub. Distinct from the existing /endpoints/splunk page, which documents the generated *.ingress.axiom.co Splunk-compatible endpoint rather than the native edge HEC service. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📝 Vale prose report🔵 4 suggestions
Advisory only — this check never blocks the PR. ℹ️ How to read this & when it's fine to ignoreThis is advisory prose linting (Vale with the Google developer style guide). It is guidance, not a gate — nothing here blocks the merge. Fix the suggestions that improve the writing (contractions, first-person "we", terminology). It's expected that some won't make sense — ignore those. Vale reads Markdown as prose, so it sometimes flags code, identifiers, product/UI names, or example data that only look like prose. Those are false positives; leaving them is the right call. To silence a false positive at the source:
If a rule is consistently wrong for our docs, propose disabling it in |
Add a v1-edge-hec OpenAPI document covering the HEC event, raw, bare collector alias, and health endpoints (served from hec.AXIOM_DOMAIN), with HecEvent/HecStatus schemas and the Splunk/Bearer/Basic auth scheme. Register it in lib/openapi.ts, add operation pages for the event, raw, and health endpoints under the Edge endpoints nav group, and cover the new spec in the OpenAPI test. A separate document rather than an addition to v1-edge-ingest because HEC lives on its own host (hec.AXIOM_DOMAIN) with the /services/collector base path, distinct from the edge ingest server. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
benenharrington
approved these changes
Aug 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a Send data guide for the Splunk HTTP Event Collector (HEC) compatible API served from the edge (hec.AXIOM_DOMAIN): the event, raw and health endpoints, the Splunk/Bearer/Basic auth schemes, index → dataset resolution, event-envelope field mapping, gzip payloads, and the Splunk response-code table. Link it from the send-data methods hub.
Distinct from the existing /endpoints/splunk page, which documents the generated *.ingress.axiom.co Splunk-compatible endpoint rather than the native edge HEC service.