Splunk® App for Infrastructure (Legacy)

Install and Upgrade Splunk App for Infrastructure

Acrobat logo Download manual as PDF


This documentation does not apply to the most recent version of Splunk® App for Infrastructure (Legacy). For documentation on the most recent version, go to the latest release.
Acrobat logo Download topic as PDF

Share data in Splunk App for Infrastructure

When the Splunk App for Infrastructure (SAI) is deployed on Splunk Enterprise, the Splunk platform sends data to Splunk Inc. ("Splunk"), and uses such data in accordance with the choices you made at the platform level. For information about how to opt in or out, and how the data is collected, stored, and governed, see Share data in Splunk Enterprise.

What data is collected

SAI collects the following additional basic usage information.

Component Description Example
app.session.deployment.type Shares whether you are using SAI or Splunk Insights for Infrastructure and the current page.
{
  app: splunk_app_infrastructure    
  deploymentType: INSIGHT    
  page: investigate    
 }
app.session.monitoringInsightsPageLoad Collects the page load time in milliseconds for each page visited to understand how the app is performing.
{
  app: splunk_app_infrastructure
  loadTime: 7397.100000000137
  metadata: {
        count: 328
        currentTab: ENTITY
        selectedView: LIST_VIEW
      }
  mode: production
  page: SiiInvestigatePage
}
app.session.sai_ui_errors Collects the error stacktrace associated with a page crash to understand why the app crashed.
{
  app: splunk_app_infrastructure
  componentStack: 
 in Connect(ConfigurePageContentsContainer)
 in Profiler (created by PageLoadProfiler)
 in PageLoadProfiler
 in ErrorBoundary (created by ErrorBoundarySai)
 in ErrorBoundarySai
 in Provider
  error: Cannot read property 'loadUserRoles' of undefined
  mode: test
  page: configure
}
app.sii.alert_definitions Collects the hashed alert title, alert metric, and alert aggregation model to understand usage around alert creation.
{ 
  alert_aggregation_method: Avg
  alert_metric_name: cpu.idle
  hashed_alert_title: af62ee3e8d96d58199f28ec9aa7a1d
}
app.sii.app_version Collects the version of the app to understand new version adoption and usage.
{ 
  app_name: Splunk App for Infrastructure 
  app_version:  1.2.2
}
app.sii.group_definitions Collects the title, dimension key, and dimension value used to create each group to track the number of groups you create. The title and dimension value is always hashed, and the dimension key is hashed if you created it.
{ 
  dimension_value: mnjnkcxzjkjk2389
  dimension_key: dslkjksdiofuiuo3489589
  title: kjhdsfhk4534&SD
}
app.sii.os_type Collects a count of hashed OS names that collectd forwards to understand the diversity of entity types.
{
  os_count: 43
  os_name: shk98sjckduy3ba8&ksd
}
Last modified on 25 September, 2019
PREVIOUS
Licensing the Splunk App for Infrastructure
  NEXT
System requirements for Splunk App for Infrastructure

This documentation applies to the following versions of Splunk® App for Infrastructure (Legacy): 1.3.0, 1.3.1, 1.4.0, 1.4.1


Was this documentation topic helpful?


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