Custom Dashboards

Custom dashboards are shared across your organization, and users can view each other’s custom dashboards in the management view. Note that any changes you make are global, and will appear for users across the entire organization.

Manage Dashboards

When you have either a Business or Trial Plan, navigating to Dashboards takes you to a view where you can manage dashboards instead of the default dashboard. From here, you can:

Manage mode.

Create Dashboards

Clicking "Create Dashboard" takes you to a new dashboard where you can immediately begin adding widgets. When you're creating a new dashboard or editing an existing one, the widgets are slightly grayed out. From here, you can:

  • Rename the dashboard
  • Add and remove widgets
  • Rearrange existing widgets
  • Resize existing widgets

Edit mode.

Create Dashboards From Templates

When the "Show Templates" toggle is enabled, several default dashboard templates are displayed. You can add each template directly to the list of dashboards by clicking "Add Dashboard", or preview it by clicking "Preview". You have to add a template before you can edit the resulting dashboard. You can also duplicate or delete a dashboard created from a template (this does not delete the template).

Widget Builder

When you add a widget or edit an existing one, you’ll be prompted with a form and preview of the visualization. From here, you can:

  • Rename the widget
  • Change the queries
  • Provide legend aliases
  • Change the Y-Axes

Widget builder.

The form includes these fields:

  • Widget Name: The name that appears at the top of each widget.
  • Visualization Display: The selected visualization type.
  • Query: The search parameters that define what you are investigating. Add additional queries to compare projects, organizations, releases, and so on. Each query has a legend alias you can name to view more easily in any of the time series charts. For more information on how to build a query, check out some of the rules we have for our Discover Query Builder.
  • Y-Axis: The attribute of the search parameters you want to map out. By default, count() is selected. Changing this to a duration will change the Y-Axis to milliseconds or seconds. Adding an overlay will add another set of data to compare. For example, to reflect P50, P75, and P90, you’ll require three overlays. If the units conflict, the charts will always base it off the first line.

Visualization Types

Line, Bar, and Area Charts

Line, bar, and area chart visualizations allow you to plot one or more aggregate functions as a time series.

Time series widgets.

Each chart type allows you to solve different problems:

  • Line charts are a general-purpose visualization. Make sure the Y-Axis units match if you add multiple overlays. Mixing count with duration will not yield useful results.
  • Bar charts will group results by day, making them good for daily roll-ups or as 'big picture' summaries. An example would be 'count of errors per day'.
  • Area charts are ideal for showing results that are cumulative or where you want to show a breakdown. An example would be 'count of errors for each major browser'.

Table Results

Table results display the top results of a Discover Query. This visualization is well suited to showing key fields and related aggregates. For example 'duration percentiles for the most frequently visited transaction names'. You can also choose to display issues data in a table visualization using the data set selector.

World Map

Events are queried using the given function and geo.country_code. The results are plotted as a density value on a world map. An example scenario would be 'in which countries are users experiencing the most errors'. You can zoom the map using the mouse wheel, or pan the map by clicking and dragging the map around.

Big Number

A big number visualization displays the current value of a single function. This visualization is well suited for high-level aggregates. An example scenario would be 'p95 of all transactions'.

Data Set Selection

Select between events and issues data in a widget with the "Data Set" selector.

Choosing "All Events" allows you to query and aggregate error and transaction events in the same way you would for a Discover query. Some widget examples include:

  • Tracking performance of an endpoint
  • Throughput by country
  • Users most affected by errors

Choosing "Issues" 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. Choose this data set if you want to customize a list of issues on your dashboard. Some widget examples include:

  • Issues assigned to your team
  • Most frequently occurring issues

The "Issues" data set is only available in table visualization widgets.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").