Splunk® Enterprise

Dashboards and Visualizations

Working with dashboard panels

A dashboard contains one or more panels. Dashboard panels use searches to generate visualizations. Select a panel type depending on the type of search behavior and configuration options that you want.

Inline panel

An inline panel contains a search directly in its source code. The search generates the results rendered in the panel visualization. You can edit an inline search using the dashboard editor.

Panel from a report

This panel type uses the saved search and visualization from a report.

When using a panel from a report, you cannot modify the search string in the panel, but you can change and configure the visualization. If the report search changes, the panel using that report updates accordingly.

Access and performance considerations

Depending on your deployment, you might need to adjust report configurations for dashboard performance and access. For instance, depending on your permissions, you can control whether the report is accelerated, scheduled, or embedded. You can also change the report permissions.

User context

Reports in dashboard panels can run as the report owner or the report user. These settings can affect data visibility and concurrent search limits.

Option Description Data visibility impact Concurrent search limit impact
Run as owner (default) Run the report using the permissions of the user who created the report.

Scheduled reports always run using report owner permissions.
A report run with owner permissions renders search results that some users might not otherwise have permission to see. In some cases, you might want to provide this kind of access. In other cases, you might want to restrict search result visibility. If a dashboard containing a report-backed panel loads multiple times simultaneously, it can impact the report owner's concurrent search limit. When the limit is reached, the report scheduler causes additional report search runs to be queued for later execution.

Dashboard users might see slower panel loading and the report owner might not be able to run searches and reports immediately.
Run as user Run the report with the permissions of the user viewing the dashboard.

Scheduled reports cannot run with user permissions.
If the report accesses data that the current user does not have permission to see, the panel does not render those results. When the report runs, it counts against the concurrent search limit of the user loading the dashboard, not the report owner.


Use scheduled reports for dashboard panels when possible

Back dashboard panels with scheduled reports whenever possible to reduce search processing load for your Splunk deployment.

Benefits of scheduled reports
Not using scheduled reports can impact search processing loads and concurrent search limits. For example, If fifty users access a particular dashboard, panels not backed by scheduled reports cause their reports to rerun fifty times.

Scheduled reports do not require the search to run each time a user loads the dashboard. Panels backed by scheduled reports show results from the last scheduled run of the report.

Using real-time scheduled reports
To show dashboard users the most current results, back dashboard panels with real-time scheduled reports. This report type runs in the background at all times. It does not launch a new report instance each time a user loads the dashboard. Instead, it shows results for the currently running real-time scheduled report.

Prebuilt panel

Save and reuse Simple XML panels in multiple dashboards. You can display a prebuilt panel in a dashboard by using a reference to the panel. Edit the panel directly to change the title, search, or visualizations in it.

Additional information

Last modified on 01 November, 2016
Create a dashboard   Add panels to dashboards

This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.0, 8.1.1, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.11, 8.1.13, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.1.7, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.2.4, 9.3.0, 9.3.1, 9.3.2, 9.4.0, 8.1.10, 8.1.12, 8.1.14, 8.1.2


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters