# Implement telemetry for the remote server \(\#59692\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/479bce099509394aa121c2c5c1cf8f2639bbc7e9)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 479bce099509394aa121c2c5c1cf8f2639bbc7e9

Requested commit: 479bce099509394aa121c2c5c1cf8f2639bbc7e9

Commit: 479bce099509394aa121c2c5c1cf8f2639bbc7e9

Tree: 4219c631bc1be8d88f8beb2ef651a74c8a23fbff

Author: Lukas Wirth

Committer: GitHub

## Message

```
Implement telemetry for the remote server (#59692)

# Objective

Telemetry events generated **on a remote server** were silently dropped,
and all remote telemetry that *was* reported got attributed to the local
client's OS.

## Solution

This PR makes server-originated events flow to the telemetry pipeline
and attributes them to the actual remote host (connection type, OS,
version, architecture), plus adds a transport-agnostic connection event.

## Additional Notes

This removes the "SSH Project Opened" event and replaces it with a
"Remote Connection Established" one that has more structured info and is
also more useful in where it gets invoked.

The server unconditionally sends back telemetry to the client, the
client is then responsible for filtering on whether telemetry is enabled
by the user or not as the server does not have knowledge of those
settings itself.

Release Notes:

- N/A
```

## Parents

- [14f9b9d077ea4de768408aa3bed285baacea13b0](https://git.cafe/gitcafe/zed/commit/14f9b9d077ea4de768408aa3bed285baacea13b0?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/479bce099509394aa121c2c5c1cf8f2639bbc7e9?format=markdown)