Create a Custom Dashboard

You can create a custom dashboard that meets your specific requirements.

1. Go to the Dashboards page.
2. Click Create dashboard.
   A blank, untitled dashboard is displayed. In the lower half of the blank dashboard, you can add or create a widget, and in the upper half, you can add filters to apply on each widget. On the right side, the About, Widgets, and Filters tabs are displayed. The Widgets and Filters tabs list all the Oracle-defined widgets and filters that you can use in the custom dashboard. To indicate the Observability & Management service for which the widgets and filters are created, an abbreviated version of the name of the service is displayed in the upper-right corner of each tile. Here's the list of the abbreviated names of the services:

   • Application Performance Monitoring – APM
   • Database Management – DBM
   • Log Analytics – LOGAN
   • Management Agent – AGENT
   • Management Dashboards – DASHBD
   • Ops Insights – OPSI
   • Stack Monitoring – STMON
3. In the upper-right corner of the dashboard, select a time period for which you want to display data in the widgets in the dashboard.
4. On the About tab, enter a name for the dashboard, select the compartment in which you want the dashboard to reside, and optionally add a description for the dashboard.
   Optionally, you can:

   • Deselect the Auto-apply filters check box to ensure that the filters added to specify the input for the widgets in the dashboard are not applied automatically as soon as you add the filter or make a change to it. By default, the Auto-apply filters check box is selected and the filters are applied automatically. On deselecting this check box, an Apply button is displayed in the filters section in the upper half of the dashboard, which you must click to apply all the changes to the filters and refresh widget data simultaneously.
   • Click Show advanced options to add free-form or defined tags to the dashboard. If you have the permissions required to create a dashboard, then you also have permissions to add free-form tags. To add a defined tag, you must have permissions to use the tag namespace. For information on:
     • Tagging concepts and the permissions required to work with tags, see Overview of Tagging.
     • How to add a tag during resource creation, see To add a tag during resource creation.
5. On the Widgets tab, you can:
   • Select the compartment and add an Oracle-defined widget from the list of available widgets, to the new dashboard. You can search for a particular widget or all the widgets created for a particular service by adding the title of the widget or the abbreviated name of the provider service to the search field above the list. For example, enter APM in the search field to only view Application Performance Monitoring widgets.

     Click the Launch widgets table view icon () to view the widget library in a tabular format. In the Widget library table view panel, click the Applied filters to select alternate options and filter the list of widgets or use the Search and Filter field to search for widgets or filter the widget list. Click Apply changes to the widget library to view the filtered list on the Widgets tab.

   • Click the Add widget group and widgets icon () to create a custom widget and add it to the new dashboard. Custom widgets are of two types, metric data explorer widgets and query-based widgets. For information on:
     • Metric data explorer widgets, see Create a Metric Data Explorer Widget.
     • Query-based widgets, see Create a Query-based Widget.

   As you click or drag and drop an Oracle-defined widget to add it to the new dashboard or select an option to create a custom widget, the required widget inputs such as compartment are automatically configured to use the corresponding filter. For certain Oracle-defined widgets that require input parameters that have internal dependencies, the widget inputs are automatically configured to use the corresponding filters. For example, when adding an Application Performance Monitoring widget, the APM domain input is dependent on the compartment input, and both are automatically configured to use the corresponding filters.

   Click Edit widgets on the Widgets tab and then click the name of the widget to view the details of the widget and make changes, if required, to the widget label, description, and the automatically configured widget inputs. The required inputs configured when adding the widget and optional inputs, if any, are listed in the Configured widget inputs section. The required inputs are denoted by an asterisk. Click the Edit icon () adjacent to each input to edit the input configuration for the widget, if required. On clicking the Edit icon (), the Configure <name> input for <name of widget>... dialog box is displayed. Select from the options in this dialog box to edit or configure the input:

   • Link the input with an existing filter: Select to link the input to an existing filter in the dashboard. Note that this option is only displayed if a filter related to the input has already been added to the dashboard.
   • Add new filter: Select to link the input to a filter available in the filter library. When you use this option, the value specified in the selected filter can be shared with other widgets that might be linked to this filter, and any change to this value will impact all the linked widgets.
   • Specify the input: Select to specify a fixed value of the input, which will be used only in the context of this widget. If you use this option, a filter is not added to the dashboard as the fixed input value is only configured for a single widget.

   Widget inputs that are not linked to a dashboard filter can be configured to act as a local filter for the widget. To do so, select the Is editable by viewers check box either when adding the widget to the dashboard or later by editing it. If this option is enabled, the widget input acts as a local filter and is displayed at the top of the widget. For example, when you add the Oracle-defined Metric line chart widget to a dashboard, the Configure Metric name input for Metric line chart (Required) dialog box is displayed. You can select the Is editable by viewers check box to make the Metric name input an interactive local filter, which is displayed above the widget. After the dashboard is created, other users of this dashboard (viewers) can change the value for that input, making the widget more interactive. In addition, viewers can click the icon in the upper-right corner of the widget to add editable widget inputs as local filters and filter the data displayed in the widget.

6. Optionally, on the Filters tab, click Edit filters to view the filters used to specify the input for the widget, make changes to the filter label and description, and click the Edit icon () adjacent to each filter input to view and modify the configuration. For example, for the Compartment filter, edit the Include subcompartments... input and select Yes to view the Subcompartments check box in the filter. Once you add a widget that can display data from subcompartments, for example, the Database top consumers widget for Ops Insights, you can select the Subcompartments check box in the Compartment filter to view that data in the widget.
   You can click Add filters on the Filters tab and click or drag and drop additional Oracle-defined filters to the upper half of the dashboard. As you add filters to the dashboard, an additional input may be required and the additional input is automatically configured to use the corresponding filter. After adding filters to the dashboard, you can also select a different option in the drop-down list on the filter to view data within its context.

   Note
   
   

   • If you've linked the same filter to multiple widgets in a dashboard, then any change made to that filter impacts all the dependent widgets.
   • If your dashboard has widgets from multiple Oracle Cloud Infrastructure Observability & Management services, then the widget data may be available in different compartments or associated with different resources. In such cases, it's helpful to define separate filters for the widgets.
7. Optionally, click the Actions icon () on a widget or filter in the dashboard to perform tasks such as altering its size or placement or deleting the widget or filter from the dashboard.
8. Click Save changes to save the new dashboard.

The dashboard is now in view mode. In the view mode, click the Actions icon () on a widget to use the following options:

• Export to CSV: Select to export widget data to a CSV file. Note that the Export to CSV option is disabled if the widget does not support this feature.
• Maximize: Select to enlarge the widget to take up the entire available space in the dashboard, providing a clearer view of the data. While viewing data in an enlarged widget, the filters set for the dashboard continue to be displayed and you can make changes to view updated data. To restore the widget to its normal size, click Restore.
• Open widget control panel: Select to display the local filter controls for the widget. Click the icon to add local filters, and select Show label to display filter labels instead of only filter values. When local filters are displayed, the Open widget control panel option is replaced by Close widget control panel.

After creating a custom dashboard, you can click in the upper-right corner of the dashboard and select one of the following options:

• Edit: Open the dashboard in edit mode.
• Duplicate: Create a duplicate of the Oracle-defined dashboard and customize it to meet your requirements.
• Export: Export the dashboard in JSON format.
• Print: Print the dashboard.
• Generate report: Generate and download a report with the current view of widgets in the dashboard, in PDF format.
  Note
  
  The Generate report feature is not supported in the Firefox and Safari browsers.
• Auto-refresh: Specify the frequency at which the data in the dashboard must be refreshed automatically.
• Refresh: Refresh the data in the dashboard.

Note that you can create a dashboard in the console and using API. For API information, see Management Dashboards API.