Logs product

[annikaschmid]

Feature request

Users have asked for a logging product, we should build it! I am adding this issue to our roadmap, so we can gauge demand for this.

Basics:

• Log Collection: Capture logs from web apps or other digital tools in real-time, supporting structured (JSON, XML) and unstructured (plain text) log formats.
• Centralized Dashboard: View and filter logs by source, severity, timestamp, or keywords, all from a unified interface.
• Search & Filtering: Easily search and filter logs based on customizable parameters (e.g., user ID, request ID) to find specific entries quickly.
• Error Tracking & Alerting: Automatically flag errors and alert relevant team members based on severity levels or specific keywords.

Questions for the Community:

• Would you use this? What would your use case be?
• Would this replace an existing tool in your current workflow? If so, which one?
• What additional features would be critical for your needs?

If you like this idea, please leave a 👍 or ❤️ reaction on this post to vote for it -- your votes and feedback help us prioritize what to work on next!

[willsr]

This would be great! We currently use Highlight.io AND Posthog. Would be good to combine both.

[buhama]

Would be amazing and would fit right in with session replays. Kind of how in LogRocket you can do LogRocket.error('');

• Would definitely use this. Use it for logging errors and other debugging information for a session
• Yes would replace GCP logs / Logrocket
• Linking to sessions and people. Filtering. Grouping. Trace Id

[Gaket]

I would expect much more traction in this ticket!

Logging system like Sentry or Datadog seems to be one the must-have tools in any startup.

So yes, I'd use it to send logs, see metrics and set up alerts based on them.

Ideally, backend, frontend, mobile.

Replaces tools like Datadog.

[vijaystroup]

+1

[TaylorFacen]

+1 I can't wait to try the new error tracking feature that was announced today. Logging will allow me to solely use PostHog for everything.

[scazan]

+1!

[nahtnam]

This was announced recently: https://blog.sentry.io/logs-in-sentry-open-beta/

[tony-garcia]

We would definitely be interested in this. Having searchable structured logs capture that are also linked to error reports, for context around fixing bugs would be great. In summary, having at least feature parity with Sentry error monitoring and logging would allow us to use PostHog for what we're currently using Sentry for: https://x.com/getsentry/status/1924863884952772787

[cloudatlas9]

Proper logging with severerities etc. and covering client-side and server-side would be so amazing. Would allow us to use Posthog as the only all-inclusive analytics/management suite and replace Sentry.

[zip-fa]

I’ll leave it here: https://github.com/PostHog/posthog/pull/35322

Maybe this will help team to start with JSON ingestion

[jamesefhawkins]

update - we've decided we should ship this! watch this space

[nattaylor]

I'm late to this party, but I would use this instead of reaching for something like DataDog log explorer.

I would use the basics listed above and don't need more, though it would be pretty cool if they were all deeplinked such that if I log a user_id or session_id then it deeplinks into that Posthog product. I would like it to be easy to implement in a Python application.

[srex-dev]

I can do this. I have done this. I'm currently doing this. I architected, built, and currently deploying basically the same thing at my corp job, but also leverages ML for model training as well as AI enriched analysis to provide end users for arming (not weaponizing!) them with more information then they actually know what to do with. Because often they don't know what they've got.

[wturon]

Currently looking for a better logging tool. Would love it if i could just use posthog for this.