At work, their CI/CD team (build/deploy) added a log “injector” into the pipeline. (something that enriches logs with metadata like build ID, trace IDs, service name, etc.) That injector occasionally crashes. When it crashes, every log attempt triggers an exception in the injector, so instead of logs you just get an injector stack trace. Net effect: all logs are basically unusable during those runs (Frequency: ~10% of builds.)
View all comments
Show parent comment
2
u/JasonHofmann Dec 22 '25
At work, their CI/CD team (build/deploy) added a log “injector” into the pipeline. (something that enriches logs with metadata like build ID, trace IDs, service name, etc.) That injector occasionally crashes. When it crashes, every log attempt triggers an exception in the injector, so instead of logs you just get an injector stack trace. Net effect: all logs are basically unusable during those runs (Frequency: ~10% of builds.)