From fabc14355c176c13710f6e76a85e3ac52b3545e1 Mon Sep 17 00:00:00 2001 From: "Joseph T. Lyons" Date: Wed, 23 Oct 2024 00:36:43 -0400 Subject: [PATCH] Update telemetry docs to not point to specific lines of code (#19583) The old links pointed to specific lines that were no longer the correct lines. Let's skip pointing the reader of the docs to a specific line. Release Notes: - N/A --- docs/src/telemetry.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/telemetry.md b/docs/src/telemetry.md index dd6556c24f0b9a0f6c0c6dea8e158a2dc75b7b05..7267bbdc0c78346feefda8e7d0802e232d7b1978 100644 --- a/docs/src/telemetry.md +++ b/docs/src/telemetry.md @@ -31,7 +31,7 @@ Telemetry is sent from the application to our servers. Data is proxied through o Diagnostic events include debug information (stack traces) from crash reports. Reports are sent on the first application launch after the crash occurred. We've built dashboards that allow us to visualize the frequency and severity of issues experienced by users. Having these reports sent automatically allows us to begin implementing fixes without the user needing to file a report in our issue tracker. The plots in the dashboards also give us an informal measurement of the stability of Zed. -You can see what data is sent when a panic occurs by inspecting the `Panic` struct in [crates/telemetry_events/src/telemetry_events.rs](https://github.com/zed-industries/zed/blob/main/crates/telemetry_events/src/telemetry_events.rs#L184) in the Zed repo. You can find additional information in the [Debugging Crashes](./development/debugging-crashes.md) documentation. +You can see what data is sent when a panic occurs by inspecting the `Panic` struct in [crates/telemetry_events/src/telemetry_events.rs](https://github.com/zed-industries/zed/blob/main/crates/telemetry_events/src/telemetry_events.rs) in the Zed repo. You can find additional information in the [Debugging Crashes](./development/debugging-crashes.md) documentation. ### Usage Data (Metrics) {#metrics} @@ -48,7 +48,7 @@ Usage Data is associated with a secure random telemetry ID which may be linked t You can audit the metrics data that Zed has reported by running the command {#action zed::OpenTelemetryLog} from the command palette, or clicking `Help > View Telemetry Log` in the application menu. -You can see the full list of the event types and exactly the data sent for each by inspecting the `Event` enum and the associated structs in [crates/telemetry_events/src/telemetry_events.rs](https://github.com/zed-industries/zed/blob/main/crates/telemetry_events/src/telemetry_events.rs#L63) in the Zed repository. +You can see the full list of the event types and exactly the data sent for each by inspecting the `Event` enum and the associated structs in [crates/telemetry_events/src/telemetry_events.rs](https://github.com/zed-industries/zed/blob/main/crates/telemetry_events/src/telemetry_events.rs) in the Zed repository. ## Concerns and Questions