Add client_filename logging and /api/collection endpoint#1
Merged
Neo23x0 merged 2 commits intoNextron-Labs:mainfrom Feb 24, 2026
Merged
Add client_filename logging and /api/collection endpoint#1Neo23x0 merged 2 commits intoNextron-Labs:mainfrom
Neo23x0 merged 2 commits intoNextron-Labs:mainfrom
Conversation
- JSONL log entries now include client_filename (original path from multipart upload)
- New /api/collection endpoint for collector begin/end markers
- POST {type:begin} returns {scan_id:<uuid>}
- POST {type:end, scan_id, stats} logs collection completion
…point Implementation guide for the collection session feature: endpoint spec, request/response formats, error handling, sequence diagram, and notes on which collectors currently implement it.
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.
Summary
Two additions to support improved collector testing and collection run tracking.
1.
client_filenamein JSONL logJSONL log entries now include a
client_filenamefield containing the original filename from the multipart upload (as submitted by the collector). Previously only the UUID-based storage path was logged, making it difficult to correlate log entries with source files in automated tests.2.
/api/collectionendpointNew
POST /api/collectionendpoint for collector begin/end markers:POST /api/collectionwith{"type":"begin", "source":"hostname", "collector":"bash/0.4.0", "timestamp":"..."}{"scan_id":"<uuid>"}POST /api/collectionwith{"type":"end", "scan_id":"...", "stats":{"scanned":100, "submitted":80, ...}}{"ok":true}This enables collectors to bracket their runs with start/end markers. The server assigns a
scan_idthat collectors can include in subsequent upload requests (&scan_id=<id>), allowing the server to group uploads by collection run.The endpoint is designed for forward compatibility — collectors that use it will silently handle 404 if the server does not support it yet.
Related