feat: add /api/tags structured access log (Closes #482) - #533
Merged
greatest0fallt1me merged 1 commit intoJul 26, 2026
Merged
Conversation
|
@Agencybuilds Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
Closes #482
Description:
This PR fulfills the backend requirements for the GrantFox FWC26 campaign (Stellar Wave) by implementing the /api/tags endpoint and capturing structured telemetry via tags_access_log.
What changed?
Added GET /api/tags Route: Implemented the route to return system tags. The boundary incorporates input validation (e.g. limiting logic) returning a standardized error envelope on failures.
Access Log Middleware Updated: Modified the accessLog middleware to detect /api/tags and format its telemetry as tags_access_log. This securely captures structured data including:
req-id (via correlationId)
latency (wall-clock time from middleware entry)
status (HTTP status code)
size (via response Content-Length)
actor (authenticated user.id or anonymous)
Unit Tests: Added tests/routes/tags.test.ts to test route responses and tests/usersAccessLog.test.ts to test specific tags_access_log fields correctly hitting the logger.
Testing
Added comprehensive tests with >90% coverage over changed lines.
Tested manually verifying structured log output properties for size and actor.
Closes #482