Rename Explore to SQL Workbench in docs (#2097)

Author: strawgate

docs/faq.md

@@ -216,7 +216,7 @@ When you're iterating on AI applications with a coding agent, the agent needs to
 
 *Logfire uses [Apache DataFusion](https://datafusion.apache.org/) as its query engine, with syntax designed to match PostgreSQL conventions.*
 
-[SQL Explorer](guides/web-ui/explore.md)
+[SQL Workbench](guides/web-ui/explore.md)
 
 ---
 

docs/guides/onboarding-checklist/add-manual-tracing.md

@@ -41,9 +41,9 @@ Note that:
 2. Spans have a start and an end time, and thus a duration. This span took 3 seconds to complete.
 3. For logs, the start and end time are the same, so they don't have a duration. But you can still see in the UI that the log was created 1 second after the span started and 2 seconds before it ended.
 
-If you click on the 'Explore' link in the top navbar, you can write SQL to explore further, e.g:
+If you click on the **SQL Workbench** link in the top navbar, you can write SQL to explore further, e.g:
 
-![Query in Explore view: select extract('seconds' from end_timestamp - start_timestamp) as duration, kind, message, trace_id, span_id, parent_span_id from records order by start_timestamp ](../../images/guide/manual-tracing-explore-basic.png)
+![Query in SQL Workbench: select extract('seconds' from end_timestamp - start_timestamp) as duration, kind, message, trace_id, span_id, parent_span_id from records order by start_timestamp ](../../images/guide/manual-tracing-explore-basic.png)
 
 Note:
 
@@ -90,7 +90,7 @@ for name in ['Alice', 'Bob', 'Carol']:
     logfire.info('Hello {name}', name=name)
 ```
 
-![Query in Explore view: select span_name, attributes->>'name' as name, message from records order by start_timestamp](../../images/guide/manual-tracing-span-names.png)
+![Query in SQL Workbench: select span_name, attributes->>'name' as name, message from records order by start_timestamp](../../images/guide/manual-tracing-span-names.png)
 
 Here you can see that:
 

docs/guides/web-ui/explore.md

@@ -1,11 +1,11 @@
 ---
-title: "Logfire SQL Explorer: Query & Inspect Your Data"
-description: Run arbitrary SQL queries against traces and metric data. Use the Logfire SQL Explorer to investigate and analyze records.
+title: "Logfire SQL Workbench: Query & Inspect Your Data"
+description: Run arbitrary SQL queries against traces and metric data. Use the Logfire SQL Workbench to investigate and analyze records.
 ---
-With **Logfire**, you can use the Explore page to run arbitrary SQL queries against your trace and metric data to
+With **Logfire**, you can use SQL Workbench to run arbitrary SQL queries against your trace and metric data to
 analyze and investigate your system.
 
-![Logfire explore screen](../../images/guide/browser-explore-full.png)
+![Logfire SQL Workbench](../../images/guide/browser-explore-full.png)
 
 ## Querying Traces
 
@@ -118,11 +118,11 @@ for the full list of metric functions.
 
 To execute a query, type or paste it into the query editor and click the "Run Query" button.
 
-![Logfire explore screen](../../images/guide/browser-explore-run-query.png)
+![Logfire SQL Workbench running a query](../../images/guide/browser-explore-run-query.png)
 
 You can modify the time range of the query using the dropdown next to the button. There is also a "Limit" dropdown that
 controls the maximum number of result rows returned.
 
-The Explore page provides a flexible interface to query your traces and metrics using standard SQL.
+SQL Workbench provides a flexible interface to query your traces and metrics using standard SQL.
 
 Happy querying! :rocket:

docs/guides/web-ui/kubernetes.md

@@ -96,7 +96,7 @@ If you have not set anything up yet, the empty state on each tab has a **Set up*
 
 ## Where Kubernetes events surface today
 
-The chart's `kubernetesEvents` preset turns Kubernetes events (pod scheduling, OOMKills, image pull failures, deployment progress) into log records via the `k8sobjects` receiver and ships them to your project. There is no dedicated **Events** tab in the Kubernetes view yet. To read them, open the [Live View](live.md) and filter on the relevant pod, namespace or `k8s.*` attribute, or query the `records` table directly in the [SQL Explorer](explore.md). Watch this space. An events feed in the Kubernetes view is in our backlog.
+The chart's `kubernetesEvents` preset turns Kubernetes events (pod scheduling, OOMKills, image pull failures, deployment progress) into log records via the `k8sobjects` receiver and ships them to your project. There is no dedicated **Events** tab in the Kubernetes view yet. To read them, open the [Live View](live.md) and filter on the relevant pod, namespace or `k8s.*` attribute, or query the `records` table directly in [SQL Workbench](explore.md). Watch this space. An events feed in the Kubernetes view is in our backlog.
 
 ## Troubleshooting
 

docs/guides/web-ui/live.md

@@ -25,7 +25,7 @@ As the greyed out `SELECT * FROM RECORDS WHERE` implies, you're searching inside
 It has auto-complete & schema hints, so try typing something to get a reminder. To run your query click `Run` or
 keyboard shortcut `cmd+enter` (or `ctrl+enter` on Windows/Linux).
 
-Note: you can run more complex queries on the [explore screen](explore.md)
+Note: you can run more complex queries in [SQL Workbench](explore.md).
 
 The records table fields are documented in the [SQL reference](../../reference/sql.md).
 

docs/guides/web-ui/llms.md

@@ -134,7 +134,7 @@ Refresh the LLMs page. A row for `gpt-4o-mini` (provider `openai`) should appear
 
 ## Slicing by environment, agent or user
 
-The inventory groups rows by `(provider, model)`. Beyond the text search at the top, there are no dropdowns for filtering by environment, agent or user *on this page yet*. For per-environment, per-agent, per-user, per-feature or per-tenant breakdowns, query the `records` table directly in the [SQL Explorer](explore.md). Every GenAI span carries the `gen_ai.*` attributes alongside `deployment.environment.name` and any custom resource attributes you've set, so you can slice cost, latency or token usage by whatever dimension matters.
+The inventory groups rows by `(provider, model)`. Beyond the text search at the top, there are no dropdowns for filtering by environment, agent or user *on this page yet*. For per-environment, per-agent, per-user, per-feature or per-tenant breakdowns, query the `records` table directly in [SQL Workbench](explore.md). Every GenAI span carries the `gen_ai.*` attributes alongside `deployment.environment.name` and any custom resource attributes you've set, so you can slice cost, latency or token usage by whatever dimension matters.
 
 ## Troubleshooting
 

docs/guides/web-ui/metrics-explorer.md

@@ -29,7 +29,7 @@ Step 3 shows you a small chart per dimension (label) on the metric, with the car
 Each card has:
 
 - **View SQL**: opens a dialog with the exact SQL that produced the chart. Copy it for a dashboard, or send it to a teammate.
-- **Open in Explore**: drops you into the [SQL Explorer](explore.md) with that query already populated, so you can extend it.
+- **Open in SQL Workbench**: opens [SQL Workbench](explore.md) with that query already populated, so you can extend it.
 
 Aggregations default sensibly by metric kind, with the rest available from the dropdown:
 
@@ -41,11 +41,11 @@ Aggregations default sensibly by metric kind, with the rest available from the d
 | Exponential histogram | `avg` | `avg`, `sum`, `min`, `max`, `count` |
 
 !!! note "Percentiles on histograms"
-    The wizard does not expose `p50`/`p95`/`p99` directly on histogram-typed metrics today: pre-aggregated histograms (e.g. `http.server.request.duration` from OTel SDK instrumentations) report `avg`, `min`, `max`, `count` and `sum` in the wizard. For percentiles over a histogram, switch to the [SQL Explorer](explore.md) and use the histogram bucket columns; the **Open in Explore** button on every card hands you a query you can extend.
+    The wizard does not expose `p50`/`p95`/`p99` directly on histogram-typed metrics today: pre-aggregated histograms (e.g. `http.server.request.duration` from OTel SDK instrumentations) report `avg`, `min`, `max`, `count` and `sum` in the wizard. For percentiles over a histogram, switch to [SQL Workbench](explore.md) and use the histogram bucket columns; the **Open in SQL Workbench** button on every card hands you a query you can extend.
 
 ## When the wizard isn't enough
 
-The wizard is for discovery. The [SQL Explorer](explore.md) is for the real work. The **View SQL** and **Open in Explore** buttons on every card are the on-ramp between them, so you can do as much as the wizard handles and graduate without retyping anything.
+The wizard is for discovery. [SQL Workbench](explore.md) is for the real work. The **View SQL** and **Open in SQL Workbench** buttons on every card are the on-ramp between them, so you can do as much as the wizard handles and graduate without retyping anything.
 
 The columns you see in the wizard live on the `metrics` table; the full schema is in the [SQL reference](../../reference/sql.md).
 
@@ -96,4 +96,4 @@ Refresh the Metrics view. `hello` appears in **Recently active** and as its own
 | Custom metric lands in **Everything else** instead of its own namespace | The metric name has no dot (e.g. `requests_total` instead of `app.requests.total`). The grouping is structural: give the name a dotted prefix to create a namespace. |
 | Step 1 shows no namespaces at all | The project hasn't received any metric samples yet. The wizard reads from `metrics`-table data; if you're sending only spans, no namespaces will appear here. |
 | Two metric sources show up under `system.*` with overlapping series | The SDK's [system-metrics integration](../../integrations/system-metrics.md) and an OpenTelemetry Collector running `hostmetricsreceiver` are both running on the same host. See the [double-counting note](#how-the-data-flows-in). |
-| Promoting a dimension shows fewer series than the cardinality card claimed | The chart truncates after a fixed number of series. For full breakdowns of a high-cardinality dimension, jump into the [SQL Explorer](explore.md) via the **Open in Explore** button on the card. |
+| Promoting a dimension shows fewer series than the cardinality card claimed | The chart truncates after a fixed number of series. For full breakdowns of a high-cardinality dimension, open [SQL Workbench](explore.md) from the **Open in SQL Workbench** button on the card. |

docs/guides/web-ui/saved-searches.md

@@ -88,5 +88,5 @@ flowchart TD
 
 **Next Steps:**
 
-- [Explore more about querying with SQL](explore.md)
+- [Learn more about querying with SQL](explore.md)
 - [Learn about dashboards and alerts](dashboards.md), (alerts.md)

docs/guides/web-ui/services.md

@@ -6,7 +6,7 @@ description: "Browse every service shipping spans to your Logfire project. See r
 
 The **Services view** is the entry point for finding the service you want to investigate. Each service that ships spans to your project appears as one row, sorted by whatever metric matters right now (requests, error rate, latency). Click a row to drill into its detail page, click a recent failed trace, and you land in the [Live View](live.md) with the failing trace open.
 
-You'll find Services in the project sidebar, between [Explore](explore.md) and [Hosts](hosts.md).
+You'll find Services in the project sidebar, between [SQL Workbench](explore.md) and [Hosts](hosts.md).
 
 ![Services inventory page](../../images/services/inventory.png)
 
@@ -36,7 +36,7 @@ You'll see:
 - **Top operations**: the highest-traffic and slowest spans inside the service.
 - **Recent errors**: a short list of failed traces, each linking straight to the [Live View](live.md) so you can investigate.
 
-Two buttons in the header ([Live view](live.md) and [Explore](explore.md)) hand the whole service off to the live view or the SQL editor in one click. The detail page defaults to the last 30 minutes.
+Two buttons in the header ([Live view](live.md) and [SQL Workbench](explore.md)) hand the whole service off to the live view or SQL Workbench in one click. The detail page defaults to the last 30 minutes.
 
 The topology graph and the operations / errors tables below the trends:
 

docs/how-to-guides/environments.md

@@ -30,7 +30,7 @@ Once set, you will see your environment in the environment picker in the Logfire
 The picker lives in the side navigation, directly below the project picker, and reads
 `all envs` until you narrow it down. It applies to observability pages like
 [Live View](../guides/web-ui/live.md), [Dashboards](../guides/web-ui/dashboards.md)
-and [Explore](../guides/web-ui/explore.md) (on pages where environments don't apply,
+and [SQL Workbench](../guides/web-ui/explore.md) (on pages where environments don't apply,
 the picker is shown disabled):
 
 ![Environments](../images/guide/environments.png)
@@ -46,7 +46,7 @@ Note that by default there are system generated environments:
 So `env not specified` is a subset of `all envs`.
 
 Any environments you create via the SDK will appear below the system generated environments.
-When you select an environment, all subsequent queries (e.g. on live view, dashboards or explore)
+When you select an environment, all subsequent queries (e.g. in Live view, Dashboards, or SQL Workbench)
 will filter by that environment. You can select more than one environment at a time, and
 hovering an environment reveals a pin icon to save it as your personal default for the
 project: that default is applied whenever you open the project.