Thomas Eizinger a6796fe8b2 fix(telemetry): always use hex-encoded ID as user ID (#9781) ...

We are currently in the process of transitioning the Firezone Clients
away from always hashing the ID before sending it to the portal. This
will make lookups and correlation of data between our systems much
easier.

The way we are performing this migration is that new installations of
Firezone will directly generate a 64 char hex-string as the Firezone ID.
If the ID looks like a UUID (which is the old format), we still hash it
and send it to the portal, otherwise we send it as-is.

Presently, the telemetry integration with Sentry and PostHog do the
opposite. They always sets the Firezone ID as-is and includes an
`external_id` that is the hashed form if it detects that it is a UUID
(or in the case of PostHog, create an alias). It is much better to flip
this around and always set the hex-string as the user id. That way, we
can simply always filter by the `user.id` attribute in Sentry and always
refer to the ID that we are seeing in the portal.

2025-07-04 16:55:44 +00:00

..

src

fix(telemetry): always use hex-encoded ID as user ID (#9781)

2025-07-04 16:55:44 +00:00

Cargo.toml

feat(rust): stream logs to Sentry when enabled in PostHog (#9635)

2025-06-25 16:14:14 +00:00