From 764c746697d178629398c330f50e9d6072589253 Mon Sep 17 00:00:00 2001 From: George Gritsouk <989898+gggritso@users.noreply.github.com> Date: Mon, 12 Jan 2026 12:27:12 -0500 Subject: [PATCH 1/3] docs(dashboards): Update Widget Builder datasets section Update the Datasets section to reflect current available datasets: - Add Spans dataset with Trace Explorer reference - Add Logs dataset with Logs Explorer reference - Add Metrics dataset with beta notice - Remove deprecated Transactions dataset - Update intro from 4 to 6 datasets Co-Authored-By: Claude Sonnet 4.5 --- .../dashboards/widget-builder/index.mdx | 41 ++++++++++++++++--- 1 file changed, 36 insertions(+), 5 deletions(-) diff --git a/docs/product/dashboards/widget-builder/index.mdx b/docs/product/dashboards/widget-builder/index.mdx index 40f9dc00f55aa..5f79c9811b72d 100644 --- a/docs/product/dashboards/widget-builder/index.mdx +++ b/docs/product/dashboards/widget-builder/index.mdx @@ -15,19 +15,50 @@ Some of these options are standard and displayed for all widgets, but others are ## Dataset -In the dataset selection step, choose which type of data you would like to use in your widget. This data is classified into four different datasets: [errors](#error), [transactions](#transactions), [issues](#issues), and [releases](#releases). +In the dataset selection step, choose which type of data you would like to use in your widget. This data is classified into six different datasets: [errors](#errors), [spans](#spans), [logs](#logs), [metrics](#metrics), [issues](#issues), and [releases](#releases). ### Errors Choosing "Errors" allows you to query and aggregate error events in the same way you would for a [Discover Query](/product/explore/discover-queries/). This data is comprised of errors that occur in your application, which Sentry will use to group into issues, for example: - Users most affected by errors -### Transactions +### Spans -Choosing "Transactions" allows you to query and aggregate transaction events in the same way you would for a [Discover Query](/product/explore/discover-queries/). This data is comprised of events that track the performance of operations in your application. Some widget examples include: +Choosing "Spans" allows you to query and aggregate individual operations within traces. Spans represent specific operations like database queries, HTTP requests, or UI rendering tasks. Each span has attributes (key-value pairs like `http.method`, `db.query`, or custom attributes) and duration information. Some widget examples include: -- Tracking performance of an endpoint -- Throughput by country +- Performance of database queries across different tables +- Average duration of API calls grouped by endpoint +- P90 latency of specific operations in your application + +You can create span-based widgets directly from [Trace Explorer](/product/explore/trace-explorer/) queries using the "Save As" button. + +### Logs + +Choosing "Logs" allows you to query and aggregate structured log data from your applications. Logs are trace-connected and searchable by message content or custom properties. This data is useful for tracking application behavior that doesn't necessarily generate errors. Some widget examples include: + +- Count of specific log events (login attempts, checkout flows) +- Logs filtered by severity level or custom attributes +- Trends in application state or business events + +You can create log-based widgets from [Logs Explorer](/product/explore/logs/) queries. + +### Metrics + + + Metrics is currently in Open Beta. Dashboard widget support for Metrics is coming soon. + + +Choosing "Metrics" allows you to track counters, gauges, and distributions from your code. Metrics are trace-connected and useful for monitoring application health signals. The three metric types are: + +- **Counters**: Track how many times something happened (e.g., `email.sent`, `checkout.failed`) +- **Gauges**: Set specific values at points in time (e.g., `queue.depth`, `memory.usage`) +- **Distributions**: Record numeric values for statistical analysis (e.g., `query.duration_ms`) + +Some widget examples include: + +- Success and failure rates for business events +- Resource utilization trends +- Application health indicators over time ### Issues From 6fc48f106a2984fe26af53a6bf556769e28d7cd1 Mon Sep 17 00:00:00 2001 From: George Gritsouk <989898+gggritso@users.noreply.github.com> Date: Tue, 13 Jan 2026 16:42:49 -0500 Subject: [PATCH 2/3] docs(dashboards): Remove Metrics dataset from Widget Builder Remove Metrics dataset section and update intro from 6 to 5 datasets. Co-Authored-By: Claude Sonnet 4.5 --- .../dashboards/widget-builder/index.mdx | 20 +------------------ 1 file changed, 1 insertion(+), 19 deletions(-) diff --git a/docs/product/dashboards/widget-builder/index.mdx b/docs/product/dashboards/widget-builder/index.mdx index 5f79c9811b72d..6f1fdce554a50 100644 --- a/docs/product/dashboards/widget-builder/index.mdx +++ b/docs/product/dashboards/widget-builder/index.mdx @@ -15,7 +15,7 @@ Some of these options are standard and displayed for all widgets, but others are ## Dataset -In the dataset selection step, choose which type of data you would like to use in your widget. This data is classified into six different datasets: [errors](#errors), [spans](#spans), [logs](#logs), [metrics](#metrics), [issues](#issues), and [releases](#releases). +In the dataset selection step, choose which type of data you would like to use in your widget. This data is classified into five different datasets: [errors](#errors), [spans](#spans), [logs](#logs), [issues](#issues), and [releases](#releases). ### Errors Choosing "Errors" allows you to query and aggregate error events in the same way you would for a [Discover Query](/product/explore/discover-queries/). This data is comprised of errors that occur in your application, which Sentry will use to group into issues, for example: @@ -42,24 +42,6 @@ Choosing "Logs" allows you to query and aggregate structured log data from your You can create log-based widgets from [Logs Explorer](/product/explore/logs/) queries. -### Metrics - - - Metrics is currently in Open Beta. Dashboard widget support for Metrics is coming soon. - - -Choosing "Metrics" allows you to track counters, gauges, and distributions from your code. Metrics are trace-connected and useful for monitoring application health signals. The three metric types are: - -- **Counters**: Track how many times something happened (e.g., `email.sent`, `checkout.failed`) -- **Gauges**: Set specific values at points in time (e.g., `queue.depth`, `memory.usage`) -- **Distributions**: Record numeric values for statistical analysis (e.g., `query.duration_ms`) - -Some widget examples include: - -- Success and failure rates for business events -- Resource utilization trends -- Application health indicators over time - ### Issues Choosing "Issues (States, Assignment, Time, etc.)" allows you to query issue properties, such as `is:unresolved` or event properties such as `error.handled:0`, and to sort by issue fields such as `First Seen`. When searching on event properties, the search will return any issue that has one or more events matching the supplied event filters. From b55a9bb0e92a3dac55fb293b0ecc9ea6ce08ff98 Mon Sep 17 00:00:00 2001 From: George Gritsouk <989898+gggritso@users.noreply.github.com> Date: Tue, 13 Jan 2026 17:00:15 -0500 Subject: [PATCH 3/3] docs(dashboards): Restore Transactions dataset and remove dataset count - Restore Transactions dataset section - Remove hardcoded dataset count to avoid stale documentation Co-Authored-By: Claude Sonnet 4.5 --- docs/product/dashboards/widget-builder/index.mdx | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/product/dashboards/widget-builder/index.mdx b/docs/product/dashboards/widget-builder/index.mdx index 6f1fdce554a50..3862672cd0177 100644 --- a/docs/product/dashboards/widget-builder/index.mdx +++ b/docs/product/dashboards/widget-builder/index.mdx @@ -15,7 +15,7 @@ Some of these options are standard and displayed for all widgets, but others are ## Dataset -In the dataset selection step, choose which type of data you would like to use in your widget. This data is classified into five different datasets: [errors](#errors), [spans](#spans), [logs](#logs), [issues](#issues), and [releases](#releases). +In the dataset selection step, choose which type of data you would like to use in your widget. Available datasets include: [errors](#errors), [spans](#spans), [transactions](#transactions), [logs](#logs), [issues](#issues), and [releases](#releases). ### Errors Choosing "Errors" allows you to query and aggregate error events in the same way you would for a [Discover Query](/product/explore/discover-queries/). This data is comprised of errors that occur in your application, which Sentry will use to group into issues, for example: @@ -32,6 +32,13 @@ Choosing "Spans" allows you to query and aggregate individual operations within You can create span-based widgets directly from [Trace Explorer](/product/explore/trace-explorer/) queries using the "Save As" button. +### Transactions + +Choosing "Transactions" allows you to query and aggregate transaction events in the same way you would for a [Discover Query](/product/explore/discover-queries/). This data is comprised of events that track the performance of operations in your application. Some widget examples include: + +- Tracking performance of an endpoint +- Throughput by country + ### Logs Choosing "Logs" allows you to query and aggregate structured log data from your applications. Logs are trace-connected and searchable by message content or custom properties. This data is useful for tracking application behavior that doesn't necessarily generate errors. Some widget examples include: