Developing Dashboards, Views, and Apps for Splunk Web


Add a table

NOTE - Splunk version 4.x reached its End of Life on October 1, 2013. Please see the migration information.

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.

Add a table

The table panel displays search results in a sortable table. You can display results in a table from just about any search, but the most interesting tables are generated from searches that include transform operations. For example, a search that uses reporting commands such as stats, chart, timechart, top, or rare. Any fields you want to display in your table should be explicitly added to your search.

For more information on table visualizations, refer to "Tables" in the Splunk Visualization Reference.

Configure the table panel

The following example displays information on processes with high CPU usage. It specifies a custom row count of 15, removes the display of row numbers, and includes a heat map overlay highlighting extreme values.

 <label>My dashboard</label>

          index="_internal" source="*metrics.log" group="pipeline" 
          | chart sum(cpu_seconds) over processor | sort -sum(cpu_seconds) 
          | rename sum(cpu_seconds) as "Total CPU Seconds"
      <title>High CPU processors</title>
      <option name="count">15</option>
      <option name="dataOverlayMode">heatmap</option>
      <option name="displayRowNumbers">false</option>
      <option name="showPager">true</option>


For basic configuration of charts, refer to the "Table panel entry" in the Panel reference for Simplified XML.

This documentation applies to the following versions of Splunk: 4.3 , 4.3.1 , 4.3.2 , 4.3.3 , 4.3.4 , 4.3.5 , 4.3.6 , 4.3.7 View the Article History for its revisions.

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

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.

Feedback submitted, thanks!