| 1 | # Diagnostics and data sharing |
| 2 | |
| 3 | The Knife does not collect or send product analytics. T3 Connect contacts its account and relay |
| 4 | services only when you use that connection option. Local diagnostics stay on your machine unless |
| 5 | you configure an export endpoint. |
| 6 | |
| 7 | ## Export diagnostics to your own receiver |
| 8 | |
| 9 | To send traces, metrics, or logs to an OpenTelemetry receiver, open |
| 10 | **Settings > General > Diagnostics**, select an environment, and enter each signal's OTLP HTTP |
| 11 | endpoint under **OpenTelemetry export** (for example `http://localhost:4318/v1/traces`). Save, then |
| 12 | restart that environment's server. The receiver must be reachable from the server's machine. |
| 13 | **Test** sends an empty export from the server to check an endpoint before or after you save it; |
| 14 | saved endpoints are checked when the section opens. Checks send authentication headers only to |
| 15 | the signal's currently running endpoint and do not follow redirects. To check a new endpoint |
| 16 | that requires authentication, save it and restart the server first. |
| 17 | |
| 18 | `T3CODE_OTLP_*_URL` and standard `OTEL_EXPORTER_OTLP_*` environment variables override the saved |
| 19 | settings. For endpoints saved here or set with `T3CODE_OTLP_*_URL`, set `T3CODE_OTLP_HEADERS` for |
| 20 | receivers that need authentication and `T3CODE_OTLP_PROTOCOL=http/protobuf` for receivers that do |
| 21 | not accept JSON. An endpoint set with `OTEL_EXPORTER_OTLP_*` takes its headers and protocol from |
| 22 | `OTEL_EXPORTER_OTLP_HEADERS` and `OTEL_EXPORTER_OTLP_PROTOCOL` instead. |