getsentry / getsentry/sentry

Allow setting properties of user outside of events

Open
#94,055 7 comments 0 reactions 1 assignee View on GitHub

@cleptric is already working on this.

Since Jun 24, 2025.

Feature Product Area: Issues
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Problem Statement

Currently, properties of a user need to be set on each event, i.e. one needs to set the user-context before starting to capture events. This means user-related information needs to be threaded through the application to the point where the SDK is initialized in order to set this information.

In our case, we have a mobile app that embeds a Rust library which has its own telemetry context (and Sentry integration). I don't want to thread the user information all the way through across the FFI boundary just so that I can set it when I initialise the Sentry SDK.

Solution Brainstorm

User IDs are already unique. It would be great if there was a separate API for attaching information to a user ID. PostHog does this with a dedicated $identify event. Other events are tied to the user ID and user information can be set separately via the $identify event.

This is great because it means we can set the user-information where it is already available.

Product Area

Issues

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.