Summary
Today, PostHog Logs on iOS 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.
Current behavior
Logs are only sent when you call them yourself:
PostHogSDK.shared.logger?.info("checkout completed", attributes: ["order_id": "ord_789"])The following are not captured automatically: os_log / Logger, print, and NSLog.
Proposed behavior
An opt-in config flag (e.g. logs.autocaptureNativeLogs = true) that hooks into os_log / Logger, print, and NSLog 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:
Posted by the mobile SDK team to gauge interest — not yet scheduled.
Summary
Today, PostHog Logs on iOS is manual capture only — you emit logs explicitly via
captureLog(...)/ theloggerAPI. 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.
Current behavior
Logs are only sent when you call them yourself:
The following are not captured automatically:
os_log/Logger,print, andNSLog.Proposed behavior
An opt-in config flag (e.g.
logs.autocaptureNativeLogs = true) that hooks intoos_log/Logger,print, andNSLogand forwards them as PostHog log records — respecting the existing severity mapping,beforeSendredaction, rate cap, and resource attributes.Related issues (other SDKs)
Same proposal is being tracked across our mobile SDKs:
Posted by the mobile SDK team to gauge interest — not yet scheduled.