Showing the changes to docs (1 of 4 files). Show all
Unified · Split
| @@ -4,9 +4,11 @@ The relay Alchemy stack owns a focused Axiom trace setup: · 3 unmodified lines | |||
| 4 | 4 | ||
| 5 | - `t3-code-relay-traces`, an OpenTelemetry trace dataset for Worker requests | 5 | - `t3-code-relay-traces`, an OpenTelemetry trace dataset for Worker requests |
| 6 | - `t3-code-relay-otel-ingest`, a dataset-scoped ingest token bound to the Worker | 6 | - `t3-code-relay-otel-ingest`, a dataset-scoped ingest token bound to the Worker |
| 7 | - `t3-code-relay-readonly-query`, a dataset-scoped token for scripted diagnostics | ||
| 8 | - `t3-code-relay-recent-spans`, a view of recent request and endpoint spans | 7 | - `t3-code-relay-recent-spans`, a view of recent request and endpoint spans |
| 9 | 8 | ||
| 9 | These are the production names. Non-production Alchemy stages append their sanitized stage name, | ||
| 10 | for example `t3-code-relay-traces-dev-julius`. | ||
| 11 | |||
| 10 | Deploy from `infra/relay` with the normal Alchemy workflow: | 12 | Deploy from `infra/relay` with the normal Alchemy workflow: |
| 11 | 13 | ||
| 12 | ```sh | 14 | ```sh |