feat(obs): add injection pipeline timing logs#147
Conversation
Add structured timing logs at key injection milestones so slow injection is visible at a glance. Info-level start/complete bookends are always shown; Debug-level intermediate steps (handshake, payload delivery, SSH client/session creation) appear with -v.
✅ Deploy Preview for devsydev canceled.
|
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 17 minutes and 31 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Replace inline 'injection: complete' logs with a single defer so early error paths (GenerateScript, os.Pipe, context.Canceled) are also covered. Add 'tunnel: setup complete' bookend via defer in runSSHTunnel.
Summary
Adds structured timing logs at key injection milestones to provide visibility into how long injection takes. After the pipe() correctness fixes, machineprovider's 5s inactivity timeout became a concern — these logs make it easy to spot slow injection at a glance.
Inject()andrunSSHTunnel()(always visible)-v)time.Since(start)for human-readable elapsed times (e.g. "1.234s")log.InitTestObserved