streamlog-knowledge

Install code.byted.org/gopkg/logs/v2 with go get, then configure a default logger in init using logs.SetWriter with console, agent, or async file writers. Use log.V2 chain APIs like Str, KV, and Obj to emit structured logs.

The v1 SDK uses format-style APIs with pure asynchronous, droppable delivery, while v2 offers chain-style APIs like Str() and Obj() with synchronous, non-dropping defaults. Versions v2.1.49 and later are compatible with most v1 APIs, so migration usually only requires changing the import path.

Replace the import path code.byted.org/gopkg/logs with code.byted.org/gopkg/logs/v2 in your code. Most v1 APIs remain compatible, but note v2 defaults to synchronous non-dropping writes, which can affect performance under heavy load.

Async writers buffer logs in a channel processed by a background goroutine, so exiting before it finishes drops pending logs. Call log.Flush() before main returns to block until all buffered logs are written.

When you wrap log.V2 calls in your own function, the reported caller points to your wrapper instead of business code. Use the CallDepth(n) API per log entry or logs.SetCallDepth() globally to adjust the call stack depth.

Use the .Limit(n) API on a single log entry to cap it at n emissions per second, preventing log storms in loops. You can also wrap a writer with writer.NewRateLimitWriter to throttle an entire output target.