feat(etl): emit info line per indexed entity-manager row#329
Merged
Conversation
The entity-manager success path logged at Debug with only type/hash/ elapsed, so in production there was no per-row signal that an EM tx indexed successfully. Promote it to an Info line carrying entity_type, action, entity_id, user_id, and block, mirroring the field set of the existing "validation rejected" and "dispatch error" logs. A single grep on hash or entity_id now shows the full lifecycle (indexed vs rejected vs errored) of every entity-manager transaction. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
raymondjacobson
changed the title
3 tasks
raymondjacobson
added a commit
to AudiusProject/api
that referenced
this pull request
Jun 1, 2026
## Summary Bumps the `go-openaudio` and `go-openaudio/pkg/etl` dependencies from `4d1c9dfdfb52` to `f6b56f1a737e`, pulling in [go-openaudio#329](OpenAudio/go-openaudio#329). That change promotes the entity-manager success path in the ETL indexer from a **Debug** `"tx indexed"` line (invisible in prod, no entity fields) to an **Info** `"entity manager indexed"` line carrying `entity_type`, `action`, `entity_id`, `user_id`, and `block`. It mirrors the field set of the existing `"entity manager validation rejected"` and `"entity manager dispatch error"` logs, so a single grep on `hash`/`entity_id` shows the full lifecycle of every EM transaction. This is the api-side bump needed to actually capture those logs in the running ETL indexer. ## Changes - `go.mod` / `go.sum`: both go-openaudio modules → `v1.3.1-0.20260601200759-f6b56f1a737e` ## Test plan - [x] `go mod tidy` stable (pins hold) - [x] `go build ./...` - [ ] After deploy, confirm `entity manager indexed` Info lines appear in the indexer logs 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
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
1 participant
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
pkg/etl/indexer.gologged at Debug with onlytype/hash/elapsed, so in production (Info level) there was no per-row signal that an EM transaction indexed successfully."entity manager indexed"carryingentity_type,action,entity_id,user_id, andblock, mirroring the field set of the existing"entity manager validation rejected"(Warn) and"entity manager dispatch error"(Error) logs.hashorentity_idnow shows the full lifecycle — indexed vs rejected vs errored — of every entity-manager transaction.Motivation
During the Python → ETL cutover we had no way to confirm from logs that individual EM rows were landing; the only visible signals were failures. This closes that gap so success is observable at the same granularity as failure.
Test plan
go build ./...inpkg/etlgo vet ./...inpkg/etlentity manager indexedline appears at Info in a deployed indexer once released🤖 Generated with Claude Code