Column and bar charts
Use column and bar charts to compare field values across a data set.
Data formatting
Column and bar charts represent one or more data series. To make sure that a search generates one or more series, check the Statistics tab. The table should have at least two columns.
Search results not structured as a table with valid x-axis or y-axis values cannot generate column or bar charts. For example, using the eval
or fields
commands might change search result structure.
Statistics table order and chart axes
Column and bar charts handle Statistics table values differently.
Column charts get x-axis values from the first column in the table. The next table columns contain y-axis values.
Bar charts get y-axis values from the first column in the table. The next table columns contain x-axis values.
As an example, any search using the timechart
reporting command generates a table where _time
is the first column. A column chart generated with this search has a _time
x-axis. A bar chart using this search has a _time
y-axis.
Single and multiple data series
Column and bar charts can visualize single or multiple data series. The following examples show you how to generate these series.
Single series
A search compares the average number of bytes passed through each source. In this search, the over
operator indicates that source
is the first table column.
...| chart avg(bytes) over source
The search produces the following table.
Column and bar charts represent this single series differently.
- Column chart
source
values are used for the x-axis. The y-axis in the column chart isavg(bytes)
.
- Bar chart
avg(bytes)
values are used for the x-axis. The bar chart y-axis would representsource
field values.
Multiple data series
To generate multiple data series, introduce the timechart
command to add a _time
field to search results. You can also change the query to introduce a split-by field.
For example, change the previous single series search by adding clientip
as a split-by field.
...| chart avg(bytes) over source by clientip
The split-by field produces multiple data series. Each clientip
is a data series with its own avg(bytes)
values for each source
.
To show multiple series in a bar or column chart, use the Format menu to configure stacking and multi-series mode.
Configuration options
Use the Format menu to customize one or more of the following column and bar chart components.
- Chart titles
- Axis titles
- Minimum and maximum axis values
- Use a logarithmic unit scale. This option is helpful when there are very small and very large axis values.
- Specify whether to abbreviate y-axis numerical values. For example, a value of 20,000 will be abbreviated to 20K if you toggle this option to On. Only y-axis values can be abbreviated in column and bar charts.
- Chart legend placement and text truncation
- Label rotation
Multiple series options
If the chart represents multiple data series, you can also configure the following options.
Multi-series mode
Compare trends across multiple series. Enable the mode to show independent axis ranges for each series.
Stacked charts
Use a stacked chart to see more details for values in a particular field. You can select unstacked, stacked, and 100% stacked bar and column charts. See the following comparison.
Stack option | Column or bar appearance | Use case |
---|---|---|
Unstacked | Columns or bars for different series appear next to each other. | An unstacked chart is useful for a lower number of series. As the number of series increases, the chart can become more difficult to understand. |
Stacked | Data points within a series appear as segments of a column or bar. The total column or bar value is the sum of all of the segments. | Use a stacked column or bar chart to highlight the relative volume, frequency, or importance of data points in a series. See the stacked chart example below. |
Stacked 100% | Each bar or column is divided into segments representing the distribution percentage for each data value in one series. | Use stacked 100% to show data distributions when there is significant segment size variation in each column or bar. |
Create a column or bar chart
Prerequisites
Review the following details about building column and bar charts.
Steps
- Write a search that generates one or more data series.
- Run the search.
- Select the Statistics tab below the search bar. The statistics table here should have two or more columns.
- Select the Visualization tab and use the Visualization Picker to select the column or bar chart visualization.
- (Optional) Use the Format menu to configure the visualization.
Examples
Bar chart
This search calculates a CPU seconds sum for each processor. The search also sorts the processors with the ten highest sums in descending order.
index=_internal "group=pipeline" | stats sum(cpu_seconds) as totalCPUSeconds by processor | sort 10 totalCPUSeconds desc
The search generates this bar chart.
Stacked column chart
This search portion aggregates events according to code values over time. The query specifies the _time
field and Code
field values to include. This query generates a series for each Code
field value.
...| timechart count by Code | fields _time L B N
The stacked columns show event counts for each code at different points in time. You can compare how many L
, B
, and N
flagged events there were at each point in time.
Pie chart | Line and area charts |
This documentation applies to the following versions of Splunk® Enterprise: 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.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.10, 8.1.11, 8.1.12, 8.1.13, 8.1.14, 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.2.0, 9.2.1, 9.2.2, 9.2.3, 9.3.0, 9.3.1
Feedback submitted, thanks!