PostHog / PostHog/posthog

Feature Request: Don't send dropped session recordings to Sentry

Open
#35,596 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature/replay
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Feature request

Is your feature request related to a problem?

If the user has a minimum duration for recordings, and the session doesn't meet that, it'll be dropped, but we'll still send the link to Sentry. This is confusing.

Describe the solution you'd like

Ideally, in such cases we'd send just the session ID and say there's no recording.

Describe alternatives you've considered

Use the session ID included in the replay link to filter events from that session: https://us.posthog.com/project/PROJECT_ID/replay/SESSION_ID (looks like this: 01983cd2-d486-757f-aaeb-80185ffcce8e)

Additional context

From: https://posthoghelp.zendesk.com/agent/tickets/34860 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/36338)

Debug info
Kind: support

Target area: session_replay

Report event: http://go/ticketByUUID/6640598a-0aa7-47c6-945c-2b697f134217

Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/01983cce-dc1d-77dc-86e8-a32922d7c0ad?t=221

Exceptions: https://us.posthog.com/project/2/error_tracking?filterGroup=%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22key%22%3A%22%24session_id%22%2C%22value%22%3A%5B%2201983cce-dc1d-77dc-86e8-a32922d7c0ad%22%5D%2C%22operator%22%3A%22exact%22%2C%22type%22%3A%22event%22%7D%5D%7D%5D%7D

Location: https://us.posthog.com/project/87592/replay/0198388b-3273-71bf-98cf-2c247fcb224e?t=133

Persons-on-events mode for project: person_id_override_properties_on_events

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the session_replay area and trace where recordings that miss the minimum duration are turned into Sentry links. Use the session ID and dropped-recording behavior described in the issue as the acceptance criteria: Sentry should receive the session ID without a recording link, and the relevant behavior should be covered by tests.

Written by the indexing model from the issue text.

Assessment

Domain
observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.