Splunk® Enterprise

Developing Views and Apps for Splunk Web

API updates and migration advice

The custom visualizations API has been updated for the latest Splunk Enterprise software version.

If you used one of the previous versions of the API to build a custom visualization app, review the following versioned changes for details and migration requirements.

Changes to existing functionality require migration to support compatibility with the custom visualizations framework. Other updates add new functionality and migration is optional.

The Splunk Custom Visualization API does not support the base (search id="baseSearch" or post-process (search base="baseSearch") searches. Change these searches to inline searches to make them compatible. For more information see Overview of search types and uses in the Splunk Dashboards and Visualizations Manual.

Backwards compatibility

App code migrated to the newest API version is no longer compatible with the previous Splunk Enterprise software version. For published apps, use versioning to support separate compatibility with different Splunk Enterprise versions.

Migrating to 6.6

Changes to existing functionality

Software version 6.6 introduces a drilldown editor user interface for visualizations saved to dashboards.

The drilldown editor is available in dashboard edit mode. As of software version 6.6, the visualization Format menu no longer includes drilldown enablement and configuration settings for Splunk platform visualizations.

After saving a visualization to a dashboard, users can use the drilldown editor or Simple XML to configure drilldown behavior.

Update Type of update Changes How to migrate

Support flag for drilldown editor availability in visualizations.conf
A new UI editor is available in Splunk Enterprise 6.6. This flag determines whether the editor is available for a visualization. Previous drilldown default behavior and configuration options in the Format menu might have changed. Remove any existing drilldown configuration options in the Format menu. Add the supports_drilldown flag to visualizations.conf and set it to true to provide the drilldown editor option in dashboards.

Drilldown enablement setting in the custom visualization. Located in savedsearches.conf.
Indicates whether drilldown is enabled by default. Default value is all (enabled). Replaces prior drilldown enablement settings in the Format editor. Remove any existing drilldown configuration options in the Format menu and use the supports_drilldown flag to make the drilldown editor available to users.

No other migration change is necessary.

New functionality in 6.6

Software version 6.6 introduces trellis layout. This feature lets users split search results on a field or aggregation to visualize values in separate segments.

Update Type of update Changes Replaces How to migrate
Support flag for trellis layout in visualizations.conf
Trellis layout lets users split search results over a field or aggregation. Visualizations appear in segments to show each field value. Adds a new UI option and menu for configuring trellis layout on visualizations. N/A Add the flag to visualizations.conf to make the trellis layout configuration menu available for the visualization.

Migrating to 6.5

Changes to existing functionality

The following updates for software version 6.5 require migration in any apps built using the previous API version.

Update Where Type of update Changes Replaces How to migrate
<splunk-control-group> formatter.html Change to supported API Provides a component for wrapping input controls with layout, labels, and help text.

CSS layout classes are deprecated and should no longer be used.
Replaces CSS layout classes for formatter controls.

Replaces separate label and help text <div> elements.
Use this component to wrap formatter.html elements instead of using <div> elements with CSS classes.

Labels and help text should no longer be declared explicitly using a separate <div>.

See the Formatter API reference for more details.
Visualization namespacing syntax formatter.html Change to supported API Provides an abbreviated syntax for referencing a visualization in the HTML file. Previous fully qualified namespacing syntax should not be used. Use the new namespacing for accuracy and stability.

See the Formatter API reference for more details.
Base visualization interface and utility class location SplunkVisualizationBase

File path change The base interface and utility class files are located in the api/ directory. These files are no longer located in the vizapi/ directory. Update any file location references in your visualization code to use the api/ directory.

New functionality in 6.5

The following updates provide new functionality in the custom visualizations framework for software version 6.5. Migration is optional but recommended.

Update Where Changes Replaces How to migrate
New utility functions SplunkVisualizationUtils Provides new utilities for accessing color palettes, formatting dates and time, and boolean normalization. N/A Use the new utility functions to access commonly needed resources or functionality.

Continue using the required security utilities.

See Utility functions in the API reference for more details.
<splunk-color-picker> formatter.html Provides a way to set a preconfigured color palette type, extend a preconfigured palette, or create a custom color palette. N/A Use one of the preconfigured color palettes or specify custom colors for extending and creating new palettes.

See the Formatter API reference for more details.
data.meta.done flag indicating search completion. visualization.js Provides a way to check for search completion. N/A Use the flag to handle large results sets from long running searches.

See Data handling guidelines for more details.
Last modified on 28 May, 2020
Custom visualizations overview   Build a custom visualization

This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 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.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.6, 8.0.10, 7.2.10, 7.0.1, 8.0.5, 8.0.8, 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.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.2.0, 9.2.1, 8.0.7, 8.0.9, 8.1.0

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