You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, PostHog Logs on Flutter is manual capture only — you emit logs explicitly via captureLog(...) / the logger API. The SDK does not automatically capture the platform's native log streams.
We're considering adding autocapture for native logs so existing logging "just works" with zero extra instrumentation, and we'd like to gauge how much demand there is before building it.
👍 this issue if you'd use it. Comments about your use case are even more helpful.
The following are not captured automatically: print, debugPrint, and dart:developer's log.
Proposed behavior
An opt-in config flag (e.g. logs.autocaptureNativeLogs = true) that hooks into print, debugPrint, and dart:developer's log and forwards them as PostHog log records — respecting the existing severity mapping, beforeSend redaction, rate cap, and resource attributes.
Related issues (other SDKs)
Same proposal is being tracked across our mobile SDKs:
Activity