log(audit): add repo + fileId to writeAuditEntry failure log#290
Merged
Conversation
Today's `console.error('writeAuditEntry failed', e)` only carries the SDK
error — there's no way to pivot Coralogix by file to tell whether failures
are concentrated on specific files or spread uniformly. Adding repo and fileId
lets us correlate failed writes with the concurrent-writer data we need to
diagnose COR-61.
No functional change: log-shape only.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Collaborator
|
🎉 This PR is included in version 1.10.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
writeAuditEntrycurrently logs only the raw SDK error on failure — no way to pivot by file in CoralogixrepoandfileIdto the error payload so failures can be correlated to specific filesMotivation (COR-61)
We have 10,055
writeAuditEntryfailures per day but can't tell whether they cluster on a handful of hot files or spread uniformly. The file identity is the missing pivot:audit.txt)This diagnostic log is the prerequisite before we can pick the right fix (COR-61).
Test plan
{ repo, fileId }next to anywriteAuditEntry failedentrieswriteAuditEntry failedentries appear for normal single-writer saves🤖 Generated with Claude Code