Skip to content

docs(dashboards): Update Widget Builder datasets section #15971

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gggritso merged 3 commits into from
Jan 20, 2026
Merged

docs(dashboards): Update Widget Builder datasets section #15971

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
764c746
docs(dashboards): Update Widget Builder datasets section
gggritso Jan 12, 2026
6fc48f1
docs(dashboards): Remove Metrics dataset from Widget Builder
gggritso Jan 13, 2026
b55a9bb
docs(dashboards): Restore Transactions dataset and remove dataset count
gggritso Jan 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 21 additions & 1 deletion docs/product/dashboards/widget-builder/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,20 +15,40 @@ 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. 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:

- Users most affected by errors

### Spans

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:

- 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.

### 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:

- 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.

### 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.
Expand Down