Splunk® IT Service Intelligence

Use Splunk IT Service Intelligence

Download manual as PDF

Download topic as PDF

Use one glass table to monitor KPI values across multiple services in ITSI

Service swapping lets you switch the context of KPIs between different services that contain the same KPIs. This lets you use one glass table to monitor KPI values across multiple services.

For example, if you have two services, both of which contain the CPU utilization % KPI, you can use service swapping to switch back and forth, and monitor CPU utilization % for both services in one glass table.

Enable service swapping

  1. In the glass tables editor, click Enable Service Swapping.
  2. Select the services that you want to use for service swapping. KPI matching is based on the KPI title, so each service must have the same KPI titles for swapping to function properly.
    Note that only services for which you have read permission are listed.
  3. Click Enable.
  4. Use the Service Swapping dropdown to switch KPI context between the selected services. When you swap services, all shared KPI values update to reflect the KPI values for the selected service.

    All KPIs that are enabled for swapping appear with a dotted bounding box in the glass table view.

If you do not want a particular KPI to be swapped when a service is swapped, select the KPI widget and set Service Swappable to No in the Configurations panel.

If you add a KPI to a glass table, the KPI automatically becomes swappable if that KPI is contained within an enabled service.

To change the services that can be swapped, click the service swapping dropdown and select Edit Service Swapping. If you do not have read permissions for one or more swappable services that were previously defined by another user, you cannot edit the services to swap.

PREVIOUS
Manage glass tables in ITSI
  NEXT
Overview of the beta glass table editor in ITSI

This documentation applies to the following versions of Splunk® IT Service Intelligence: 3.0.0, 3.0.1, 3.0.2, 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.1.0, 4.1.1, 4.1.2, 4.1.5, 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.3.0, 4.3.1


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

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