Tunnel: Enrich envelope with additional data (such as user details)

[pquerner]

Hello!

Is it possible to enrich the envelope with user information, such as their id, from the backend side during pass-through (throught the tunnel)?

I see sometimes there is more than json in the envelope and I don't want to temper with it if possible. (Specially with Replay requests)

Anyone see a way to circumvent it? Maybe only take the json from the body, leave everything as-is, add something (the user information array) to the json, repackage. Havent tried that, but that would alter the json-body and maybe Sentry doesnt like that?

(We don't currently have customers id/email etc. in the frontend, so cannot give it to Sentry during init (or after login) for that matter)

Thanks!

[pquerner]

Found https://develop.sentry.dev/sdk/envelopes/ - doesnt seem too trivial.

[AbhiPrasad]

Is it possible to enrich the envelope with user information, such as their id, from the backend side during pass-through (throught the tunnel)?

You're best bet is to open the envelopes directly and insert in this data, this is an unsupported use case for now.

Could you make-do with an anonymous ID you generate on the frontend you can correlate with customer id/email on backend?

[pquerner]

So it becomes a simple case of a string replace?

Frontend says customerid is "LALALA_MY_CUSTOMER_ID_IS_42" and in the backend (tunnel) I replace that with an actual value?

How would I null / remove that value for guests? (Is empty string okay?)

[AbhiPrasad]

So it becomes a simple case of a string replace?

Ah I meant more like doing no envelope transform and instead just using anonymous ids directly in Sentry. You could then just look the ids up separately in your own datastore.

[pquerner]

doing no envelope transform

What does that mean?

You could then just look the ids up separately in your own datastore.

How, when I don't know who it concerned during execution? I thought thats what I can give Sentry in form of "extra context" so it says, this issue report (or replay or XY) was for customer id 42.

[pquerner]

Session Replays are named after user identification. If we give the user id, replays are named just after their id.
Doing something like this, doesnt seem to work (replays have the "title" shorty, but get renamed [1] by the system automatically it seems back to the id):

Sentry.configureScope(function (scope) {
            scope.setUser({
                id: "User-Id: " + e.customer.id,
            });
        });

[1] customer id is encrypted on the frontend, while still unique the representation lacks context. We wish we could "rename" the replays to something like "User-ID: encryptedId".