ITSI REST API schema - Splunk Documentation (2024)

Table of Contents
General details ITSI backend store ITSI object types Common Attributes Entity Description Attributes Service Description Attributes Subordinate objects Service Template Description Attributes Subordinate objects Entity Rules Description Attributes Entity rules evaluation examples Entity Type Description Attributes Subordinate objects Entity Type Dashboard Drilldown Description Attributes Entity Type Data Drilldown Description Attributes Entity Type Vital Metrics Description Attributes Service KPI Description Attributes Service Template KPI Description Attributes Service Health KPI Subordinate objects KPI Threshold Settings Description Attributes Subordinate data structures KPI Threshold Levels Description Attributes KPI Threshold Templates Description Attributes KPI Base Search Description Attributes Glass Table Description Attributes Subordinate data structures Glass Table Widget Configuration Description Attributes Glass Table Icon Description Attributes Deep Dive Description Attributes Subordinate data structures Deep Dive Lane Setting Description Attributes Time Variate Thresholds Specification Description Attributes Collection details Usage Maintenance Calendar Description Attributes Event Management State Description Attributes Notable Event Group Description Attributes Notable Event Comment Description Attributes Notable Event Aggregation Policy Description Attributes Notable Event Email Template Description Attributes Correlation Search Description Attributes Service Analyzer Description Attributes Team Description Attributes Anomaly Detection Algorithm Settings Attributes Event Management Export Description Attributes

The IT Service Intelligence (ITSI) REST API schema describes the JSON-based data structures of ITSI objects. Use this schema with the ITSI REST API to create API requests and interpret API responses. See ITSI REST API reference.

General details

ITSI backend store

ITSI stores its configuration in the KV store. KV store collections for ITSI are located here:

https://<splunk_server>:8089/servicesNS/nobody/SA-ITOA/storage/collections/

Do not make any updates through the ITSI KV store collections endpoint above. Perform all operations using the REST endpoints documented in the ITSI REST API reference.

For more information about the KV store, see App Key Value Store on the Splunk developer portal.

ITSI object types

The ITSI REST API supports these object types:

  • entity
  • entity_type
  • service
  • base_service_template (service template)
  • deep_dive
  • glass_table
  • home_view (service analyzer)
  • kpi_template
  • kpi_threshold_template
  • kpi_base_search
  • event_management_state
  • notable_event
  • notable_event_group
  • notable_event_comment
  • notable_event_aggregation_policy
  • notable_event_email_template
  • correlation_search
  • maintenance_calendar
  • team

Note: The /SA-ITOA/<interface_category>/get_supported_object_types GET operation returns a list of currently supported object types. Note that although the entity_relationship and entity_relationship_rule objects are returned, these are not used at this time. For more information, see the ITSI REST API reference.

Common Attributes

The following attributes are common to all ITSI objects. These attributes are available in the model for each object type.

FieldTypeDescription
object_typeStringName of the object type.
create_byStringThe user who created this object.
create_sourceStringThe sourcetype initiating create. Has value manual for user-initiated creates. For internal use only.
create_timeStringTimestamp at the time of creation based on UTC time zone.
mod_sourceStringSourcetype initiating modification. Has value manual for user-initiated modifications. For internal use only.
mod_timeStringTimestamp of the last modification based on UTC time zone.
_ownerStringSplunk user nobody.
_userStringUser who performed the most recent operation on this object.
versionStringThe version of the object. Currently the same as the ITSI app version.

Common attributes are omitted from the object schemas in this topic to make the documentation easier to read.

Entity

Description

An entity is a basic unit of configuration in an IT environment that meets a specific need for an IT service. Entities are usually servers, but can be other IT infrastructure components, such as network devices, storage subsystems, applications, and so on. Entities are optional.

The entity object contains field aliases and values that identify the entity in KPI searches.

Attributes

FieldTypeDescription
_keyStringAuto-generated unique identifier for this entity. Can be any unique value.
titleStringName of the entity. Can be any unique value.
descriptionStringUser defined description of the entity.
object_typeStringentity
identifierObjectvalues: Array of alias values that identify the entity
fields: Array of search fields that identify events for the entity.
informationalObjectvalues: Array of alias values that provide information/description for the entity.
fields: Array of search fields to extract information/description of the entity.
servicesArrayArray of sub-objects with _key and title fields of services monitoring this entity via rules configured in services.
sec_grpStringThe team the object belongs to. The entity object can only belong to default_itsi_security_group (Global team).
sai_entity_keyStringThis field exists in ITSI entities that have been merged with SAI entities. It symbolizes the original SAI entities's _key and is used for drilldowns to SAI.
entity_type_idsArrayArray of _key values for each entity type associated with the entity.

For more information, see Overview of entity integrations in ITSI in the Entity Integrations manual.

Service

Description

An ITSI service is a representation of a real world IT service. You can configure an ITSI service to monitor various IT metrics using KPI searches, which reflect the health of a service. ITSI services can describe any real world IT service, such as a network service or email service.

The service object contains the service definition, including entities, KPIs, and dependent services.

Attributes

FieldTypeDescription
_keyStringAuto-generated unique identifier for this service.
descriptionStringUser defined description for the service.
titleStringTitle of this service.
kpisArrayArray of KPI descriptions for this service.
entity_rulesArrayArray of rules describing entities referenced by this service.
services_depends_onArrayArray of service descriptions with KPIs in those services that this service depends on.
service_idString_key value of service that this service depends on.
kpis_depending_onArrayArray of _key ids for each KPI in service identified by serviceid, which this service will depend on.
services_depending_on_meArrayAn array of service descriptions with KPIs in this service that those services depend on.
serviceidString_key value of service that depends on this service.
kpis_depending_onArrayArray of of _key ids of each KPI in this service, which the service identified by serviceid will depend on.
EnabledBooleanIf set to 1, service is enabled. If value is absent or not set to 1, service is disabled. On upgrade service is flagged as enabled.
sec_grpStringThe team the object belongs to.
base_service_template_idStringThe ID of the service template the service is linked to. Not required. If empty, the service is not linked to a service template. To create a service based on a service template, include this field.
service_tagsObjectThe tags for the service. The service_tags object can have an array for tags and template_tags. tags are regular tags that are added manually and template_tags are tags that are populated from a service template.

Tags have to be strings and can't contain the following characters: / \ " '! @? . ,; $ ^

Example service_tags object:

"service_tags": { "tags": [ "unix", "seattle" ], "template_tags": [ "cloud_systems", "us-west" ] },

For more information, see Overview of creating services in ITSI in the Service Insights manual.

Subordinate objects

  • Entity Rules
  • Service KPI

Service Template

Description

ITSI service templates help you manage shared content for similar services. Services linked to a service template receive content from the service template, such as KPIs and entity rules. You must create a service template from an existing service.

The base_service_template object contains KPI definitions, entity rules, and any linked services.

Attributes

FieldTypeDescription
_keyStringAuto-generated unique identifier for this service template.
descriptionStringUser defined description for the service template.
titleStringTitle of this service template.
kpisArrayArray of KPI descriptions for this service template.
entity_rulesArrayArray of rules describing entities referenced by this service template.
service_idString_key value of the service this service template is generated from.
sec_grpStringThe team the service template belongs to. Service templates can only belong to default_itsi_security_group (Global team).
linked_servicesArrayArray of services linked to this service template. if the user does not have access to all linked services, the linked_services field only contains the services they have read access to.
total_linked_servicesIntegerThe number of services linked to this service template.
last_sync_errorStringError message if the last sync operation failed.
sync_statusStringSync status of service template: "synced", "sync_scheduled", "syncing", "sync failed".
scheduled_timeStringThe time to push service template changes to linked services if "sync later" is selected rather than "sync now".
scheduled_jobDictSync job detail if "sync later" is selected rather than "sync now".
template_tagsArrayThe service tags contained within the template.

Subordinate objects

  • Entity Rules
  • Service Template KPI

Entity Rules

Description

entity_rules determine the specific entities that a KPI monitors in a service. This includes entities directly identified by title, and entities identified by regular expression-based rules.

Attributes

Entity rules are an array of rule groups separated by OR at the top level.

FieldTypeDescription
rule_conditionBoolean operatorUses the value AND indicating this rule appends all nested rules contained in the rule_items attribute.
rule_itemsArrayArray of rules that are appended within a rule group.
fieldStringThe field in the entity definition to compare values to evaluate this rule.
rule_typeStringTakes values not or matches to indicate whether it's an inclusion or exclusion rule. Value can be matchesblank or doesnotmatchblank when used with service templates.
valueStringValues to evaluate in the rule. To specify multiple values, separate them with a comma. Values are not case sensitive.
field_typeStringTakes values alias or info specifying in which category of fields the field attribute is located.

Entity rules evaluation examples

The following examples show how ITSI evaluates entity_rules.

Match all entities that are a given title value like Foo

"entity_rules": [ { "rule_condition": "AND", "rule_items": [ { "field": "title", "rule_type": "matches", "value": "Foo", "field_type": "title" } ] }]

Match all entities that are a given alias field named category value pattern like *Foo*

"entity_rules": [ { "rule_condition": "AND", "rule_items": [ { "field": "category", "rule_type": "matches", "value": "*Foo*", "field_type": "alias" } ] }]

Exclude all entities that are a given info field named subcategory value like Foo

"entity_rules":[ { "rule_condition": "AND", "rule_items": [ { "field": "subcategory", "rule_type": "not", "value": "Foo", "field_type": "info" } ] } ]

Exclude all entities that are a given title value pattern like *Foo*

"entity_rules":[ { "rule_condition": "AND", "rule_items": [ { "field": "title", "rule_type": "not", "value": "*Foo*", "field_type": "title" } ] } ]

Match all entities that are a given info field named subcategory value like Foo AND also are a given alias field named category value pattern like "*Bar*"
OR
Match all entities that are one of the given title value and value pattern namely Title1, *Title2* or Title3

"entity_rules":[ { "rule_condition": "AND", "rule_items": [ { "field": "category", "rule_type": "matches", "value": "*Bar*", "field_type": "alias" }, { "field": "subcategory", "rule_type": "matches", "value": "Foo", "field_type": "info" } ] }, { "rule_condition": "AND", "rule_items": [ { "field": "title", "rule_type": "matches", "value": "Title1,*title2*,Title3", "field_type": "title" } ] }]

Entity Type

Description

An entity_type defines how to classify a type of data source. For example, you can create a Linux, Windows, Unix/Linux add-on, VMware, or Kubernetes entity type. An entity type can include zero or more data drilldowns and zero or more dashboard drilldowns. You can use a single data drilldown or dashboard drilldown for multiple entity types.

Attributes

FieldTypeDescription
titleStringThe name of the entity type.
descriptionStringA description of the entity type.
dashboard_drilldownsArrayAn array of dashboard drilldown objects. Each dashboard drilldown defines an internal or external resource you specify with a URL and parameters that map to one of an entity fields. The parameters are passed to the resource when you open the URL. See Entity Type Dashboard Drilldown.
data_drilldownArrayAn array of data drilldown objects. Each data drilldown defines filters for raw data associated with entities that belong to the entity type. See Entity Type Data Drilldown.
vital_metricsArrayAn array of vital metric objects. Vital metrics are statistical calculations based on SPL searches that represent the overall health of entities of that type. See Entity Type Vital Metrics.

Subordinate objects

  • Entity Type Dashboard Drilldown
  • Entity Type Data Drilldown
  • Entity Type Vital Metrics

Entity Type Dashboard Drilldown

Description

A dashboard_drilldown lists the dashboards associated with an entity and its entity type.

Attributes

FieldTypeDescription
titleStringThe name of the dashboard.
idStringA unique identifier for the dashboard.
base_urlStringAn internal or external URL that points to the dashboard. This setting exists because for internal purposes, navigation suggestions are treated as dashboards. This setting is only required if is_splunk_dashboard is false.
is_splunk_dashboardBooleantrue if the dashboard is a Splunk XML dashboard. If it's another dashboard type such as a JSON dashboard from the Splunk Dashboards app, or if it's a navigation link, this value is false.
dashboard_typeStringThe type of dashboard being added. This element is required. The following options are available:
  • xml_dashboard - a Splunk XML dashboard. Any dashboards you add must be of this type.
  • navigation_link - a navigation URL. Should be used when base_url is specified.
paramsObjectA set of parameters for the entity dashboard drilldown that provide a mapping of a URL parameter and its alias and static parameters.

Entity Type Data Drilldown

Description

A data_drilldown is a basic unit of configuration for an entity type. Entity data drilldown specifies filters that correlate raw data in Splunk indexes with an entity.

Attributes

FieldTypeDescription
titleStringName of the drilldown.
typeStringType of raw data to associate with. Must be either metrics or events.
static_filterObjectFilter down to a subset of raw data associated with the entity using static information like sourcetype.
entity_field_filterArrayFurther filter down to the raw data associated with the entity based on a set of selected entity alias or informational fields.

Entity Type Vital Metrics

Description

vital_metrics are a basic unit of configuration for an entity type. Vital metrics are statistical calculations based on SPL searches that represent the overall health of entities of that type.

Attributes

FieldTypeDescription
metric_nameStringThe title of the vital metric. When creating vital metrics, it's a best practice to include the aggregation method and the name of the metric being calculated. For example, Average CPU usage.
searchStringThe search that computes the vital metric. The search must specify the following fields:
  • val for the value of the metric.
  • _time because the UI attempts to render changes over time. You can achieve this by adding span={time} to your search.
  • Fields as described in the split_by_fields configuration of this vital metric. For example, your search should be split by host,region if the split_by_fields configuration is [ "host", "region" ].
split_by_fieldsArrayThe fields that the search configuration is split on. Make sure the value matches the split by fields in the actual search.

For example:
search = "..... by host, region"
split_by_fields = ["host", "region"]

matching_entity_fieldsArraySpecifies the aliases of an entity to use to match with the fields specified by split_by_fields in the search result. The order of values should match the order of split_by_fields and the mapping is 1 to 1, so they must be of the same length.

For example:
split_by_fields = ["InstanceId", "region"]
matching_entity_fields = ["instance_id, zone"]

You can only use entity aliases for this field, not informational fields

is_keyBooleanIndicates if the vital metric specified is a key metric. A key metric calculates the distribution of entities associated with the entity type to indicate the overall health of the entity type. The key metric is rendered as a histogram in the Infrastructure Overview. Only one vital metric can have is_key set to true.
unitStringThe unit of the vital metric. For example, KB/s.
alert_ruleObjectDisplays vital metric alert threshold information. The following parameters are displayed:
  • suppress_time: suppress the alert until this time
  • cron_schedule: frequency of alert search
  • is_enabled: if alert is enabled
  • critical_threshold: range of values that indicate critical severity level
  • warning_threshold: range of values that indicate warning severity level
  • info_threshold: range of values that indicate info severity level
  • entity_filter: filter entities based on the field dimensions

For example:
entity_filter: [{"field":"os", "value":"Ubuntu", "field_type":"info"}]

Service KPI

Description

KPI is the data structure that drives the monitoring of service metrics. Each KPI object contains specific information, including a user-configured base search, from which ITSI generates the search that monitors a metric. KPI objects also contain information on how to apply thresholds that determine the metric severity level.

KPI objects (kpis) are defined and contained within the service object type data structure.

Attributes

FieldTypeDescription
_keyStringAuto-generated unique ID for this KPI.
titleStringUser-defined name for the KPI
descriptionStringUser-defined description for the KPI.
typeStringkpi_primary
kpi_threshold_template_idStringUser-defined ID for the KPI. Used to refer to KPIs within a KPI template in modules. This uniquely identifies a KPI template in ITSI.
isadhocBooleanIf true the search is split on entities and thresholds are computed for both entity and aggregate.
is_service_entity_filterBooleanIf true a filter is used on the search based on the entities included in the service.
datamodeStringThe data model to use for search generation if this is a data model type search.
datamodel_filterArrayITSI generated clauses for user-defined filters on top of the data model fields. Used in the KPI search to filter events required by this KPI.
threshold_fieldStringUser-specified field on which statistical operations are performed and whose value determines KPI health.
entity_statopStringStatistical operation (avg, max, mean, and so on) used to combine data for alert_values on a per entity basis (used if entity_breakdown is true).
aggregate_statopStringStatistical operation (avg, max, median, stdev, and so on) used to combine data for the aggregate alert_value (used for all KPI).
urgencyIntegerUser-assigned importance value for this KPI.
unitStringUser-defined units for the values in threshold field.
entity_id_fieldsStringFields from this KPI's search events that will be mapped to the alias fields defined in entities for the service containing this KPI. This field enables the KPI search to tie the aliases of entities to the fields from the KPI events in identifying entities at search time.
entity_alias_filtering_fieldsStringSubset of aliases from all entities included in the service containing this KPI, to restrict this KPI to only the subset of entities matching via the subset of aliases. Helps filter entities for this KPI among the ones selected in the service containing this KPI.
cron_scheduleStringThe cron schedule that determines the frequency of this KPI search.
base_searchStringKPI search defined by user for this KPI. All generated searches for the KPI are based on this search.
kpi_base_searchStringA basic search generated for the KPI search.
searchStringGenerated search for this KPI for base statistics on the threshold field.
search_entitiesStringGenerated search for this KPI for base statistics on the threshold field to use for "Per Entity" threshold type.
search_aggregateStringGenerated search for this KPI for base statistics on the threshold field to use for "Aggregate" or "Both" threshold type.
search_time_seriesStringGenerated search used primarily to show preview information in the KPI configuration page.
search_time_series_entitiesStringGenerated search used primarily to show preview information for "Per Entity" threshold type in the KPI configuration page
search_time_series_aggregateStringGenerated search used primarily to show preview information for "Aggregate" or "Both" threshold type in the KPI configuration page.
search_time_compareStringGenerated search used specifically by glass table.
search_alertStringGenerated search used for alerting based on KPI threshold. This is the search that runs on schedule via the saved search for this KPI.
search_alert_entitiesStringGenerated search to use for alerting based on KPI threshold for "Per Entity" threshold type.
search_alert_entitiesStringGenerated search to use for alerting based on KPI threshold for "Aggregate" or "Both" threshold type.
alert_onStringSpecified if the threshold type for this KPI is "Per Entity" or "Aggregate" or "Both". Possible values: aggregate, entities, both.
alert_periodStringUser specified interval to run the KPI search in minutes.
alert_lagIntegerContains the number of seconds of lag to apply to the alert search. The maximum value is 30 minutes (1800 seconds).
search_alert_earliestStringEarliest time to look for events every time KPI search runs. This determines how far back each time window is during KPI search runs.
tz_offsetStringISO time zone offset. Note: Do not change this value.
time_variate_thresholdsBooleanIf true, thresholds for alerts are pulled from time_variate_thresholds_specification.
time_variate_thresholds_specificationObjectData structure for time variate threshold specs.
backfill_enabledBooleanIndicates if backfill has been enabled for this KPI
backfill_earliest_timeStringRequested earliest time for backfill (relative time offset). Should be in the format -Xd, where 'd' means the time is in days, 'X' is number of days to backfill, and '-' means the date is in the past.
adaptive_thresholds_is_enabledBooleanDetermines if adaptive threshold is enabled for this KPI.
adaptive_thresholding_training_windowStringEarliest time for the Adaptive Threshold training algorithm to run over (latest time is always 'now') (e.g. '-7d')
anomaly_detection_is_enabledBooleanDetermines if trending anomaly detection is enabled.
cohesive_anomaly_detection_is_enabledBooleanDetermines if cohesive anomaly detection is enabled.
anomaly_detection_alerting_enabledBooleanDetermines if anomaly detection will alert for anomalies.
anomaly_detection_training_windowStringEarliest time for the training algorithm to run over (latest time is always 'now') (e.g. '-7d').
trending_adObjectData structure for trending anomaly detection algorithm settings. See Anomaly Detection Algorithm Settings.
cohesive_adObjectData structure for cohesive anomaly detection algorithm settings. See Anomaly Detection Algorithm Settings.
gap_severityStringSeverity level assigned for data gaps (info, normal, low, medium, high, critical, or unknown)
gap_severity_colorStringSeverity color assigned for data gaps.
gap_severity_color_lightStringSeverity color assigned for data gaps.
gap_severity_valueStringSeverity value assigned for data gaps.
entity_thresholdsObjectUser-defined thresholding levels for "Per Entity" threshold type. For more information, see KPI Threshold Setting.
aggregate_thresholdsObjectsUser-defined thresholding levels for "Aggregate" threshold type. For more information, see KPI Threshold Setting.
EnabledBooleanIf set to 1, KPI is enabled. If absent or not set to 1, KPI is disabled. On upgrade KPI is flagged as enabled. Field is read-only.
base_service_template_idStringThe key of service template object if the KPI is inherited from a service template.
entity_breakdown_id_fieldStringKPI search events are split by the alias field defined in entities for the service containing this KPI.
aggregate_outlier_detection_enabledBooleanIndicates if outlier exclusion is turned on for KPI.
outlier_detection_algoStringDetermines the outlier detection algorithm.
outlier_detection_sensitivityStringThe trigger threshold of the algorithm. For the standard deviation, this is the number of standard deviations. For interquartile range and mean absolute deviation, this is the sensitivity value.

Service Template KPI

Description

KPI is the data structure that drives the monitoring of service metrics. KPI objects for service templates differ slightly from KPI objects for services. For example, service template KPIs can only use base searches, not ad hoc searches or searches based on data models. You can't enable anomaly detection for service template KPIs.

KPI objects, kpis, for service templates are defined and contained within the base_service_template object type data structure.

Attributes

FieldTypeDescription
_keyStringAuto-generated unique ID for this KPI.
titleStringUser-defined name for the KPI
descriptionStringUser-defined description for the KPI.
typeStringkpi_primary.
kpi_threshold_template_idStringUser-defined ID for the KPI. Used to refer to KPIs within a KPI template in ITSI modules. This uniquely identifies a KPI template in ITSI.
is_service_entity_filterBooleanIf true a filter is used on the search based on the entities included in the service.
datamodeStringThe data model to use for search generation if this is a data model type search.
datamodel_filterArrayITSI generated clauses for user-defined filters on top of the data model fields. Used in the KPI search to filter events required by this KPI.
threshold_fieldStringUser-specified field on which statistical operations are performed and whose value determines KPI health.
entity_statopStringStatistical operation (avg, max, mean, and so on) used to combine data for alert_values on a per entity basis (used if entity_breakdown is true).
aggregate_statopStringStatistical operation (avg, max, median, stdev, and so on) used to combine data for the aggregate alert_value (used for all KPI).
urgencyIntegerUser-assigned importance value for this KPI.
unitStringUser-defined units for the values in threshold field.
entity_id_fieldsStringFields from this KPI's search events that will be mapped to the alias fields defined in entities for the service containing this KPI. This field enables the KPI search to tie the aliases of entities to the fields from the KPI events in identifying entities at search time.
entity_alias_filtering_fieldsStringSubset of aliases from all entities included in the service containing this KPI, to restrict this KPI to only the subset of entities matching via the subset of aliases. Helps filter entities for this KPI among the ones selected in the service containing this KPI.
cron_scheduleStringThe cron schedule that determines the frequency of this KPI search.
base_searchStringKPI search defined by user for this KPI. All generated searches for the KPI are based on this search.
kpi_base_searchStringA basic search generated for the KPI search.
alert_onStringSpecified if the threshold type for this KPI is "Per Entity" or "Aggregate" or "Both". Possible values: aggregate, entities, both.
alert_periodStringUser specified interval to run the KPI search in minutes.
alert_lagIntegerContains the number of seconds of lag to apply to the alert search. The maximum is 30 minutes (1800 seconds).
search_alert_earliestStringEarliest time to look for events every time KPI search runs. This determines how far back each time window is during KPI search runs.
tz_offsetStringISO time zone offset. Note: Do not change this value.
time_variate_thresholds_specification_customBooleanIf true, thresholds for alerts are pulled from time_variate_thresholds_specification.
adaptive_thresholds_is_enabledBooleanDetermines if adaptive threshold is enabled for this KPI.
adaptive_thresholding_training_windowStringEarliest time for the Adaptive Threshold training algorithm to run over (latest time is always 'now') (e.g. '-7d')
gap_severityStringSeverity level assigned for data gaps (info, normal, low, medium, high, critical, or unknown)
gap_severity_colorStringSeverity color assigned for data gaps.
gap_severity_color_lightStringSeverity color assigned for data gaps.
gap_severity_valueStringSeverity value assigned for data gaps.
entity_thresholdsObjectUser-defined thresholding levels for "Per Entity" threshold type. For more information, see KPI Threshold Setting.
aggregate_thresholdsStringUser-defined thresholding levels for "Aggregate" threshold type. For more information, see KPI Threshold Setting.
EnabledBooleanIf set to 1, KPI is enabled. If absent or not set to 1, KPI is disabled. On upgrade KPI is flagged as enabled. Field is read-only.
entity_breakdown_id_fieldStringKPI search events are split by the alias field defined in entities for the service containing this KPI.

Service Health KPI

The Service Health KPI tracks the health score of an entire service. Service Health KPIs have the same data structure as user defined KPIs.

Service Health KPIs have the following ID format:

SHKPI-<_key id for the service>

Subordinate objects

  • KPI Threshold Settings
  • Time Variate Thresholds Specification
  • Anomaly Detection Algorithm Settings

KPI Threshold Settings

Description

KPI Threshold Settings define the thresholds that a KPI uses to compute health status information. KPI Threshold Settings also contain information for rendering KPI threshold graphs.

Attributes

FieldTypeDescription
gaugeMinIntegerMinimum value for the threshold gauge specified by user.
gaugeMaxIntegerMaximum value for the threshold gauge specified by user.
searchStringGenerated search used to compute the thresholds for this KPI.
baseSeverityValueIntegerValue for base threshold level.
baseSeverityColorStringSeverity color assigned for the base threshold level.
baseSeverityColorLightStringSeverity light color assigned for the base threshold level.
baseSeverityLabelStringSeverity label assigned for the base threshold level, including info, warning, critical, etc.
metricFieldStringThresholding field from the search.
renderBoundaryMinIntegerLower bound value to use to render the graph for the thresholds.
renderBoundaryMaxIntegerUpper bound value to use to render the graph for the thresholds.
isMaxStaticBooleanTrue when maximum threshold value is a static value, false otherwise.
isMinStaticBooleanTrue when min threshold value is a static value, false otherwise.

Subordinate data structures

  • KPI Threshold Levels

KPI Threshold Levels

Description

KPI Threshold Levels determine how ITSI extracts health status information from KPI searches. Threshold levels are user-configured values that can be augmented further using adaptive thresholding.

Attributes

FieldTypeDescription
thresholdValueIntegerValue for the threshold field stats identifying this threshold level. This is the key value that defines the levels for values derived from the KPI search metrics.
severityColorStringSeverity color assigned for this threshold level.
severityColorLightStringSeverity light color assigned for this threshold level.
severityValueIntegerSeverity value assigned for this threshold level.
severityLabelStringSeverity label assigned for this threshold level like info, warning, critical, etc.
dynamicParamIntegerValue of the dynamic parameter for adaptive thresholds.

KPI Threshold Templates

Description

A kpi_threshold_template is a set of predefined threshold values that you can apply to multiple KPIs.

Attributes

FieldTypeDescription
titleStringName of this template.
descriptionStringDescription of this particular template.
adaptive_thresholding_training_windowStringEarliest time for the adaptive threshold training algorithm to run over. The latest time is always now.
time_variate_thresholdsBooleanIf true, thresholds for alerts are pulled from time_variate_thresholds_specification.
Time_variate_thresholds_specificationObjectData structure for time variate threshold specification.
adaptive_thresholds_is_enabledBooleanIf true, adaptive thresholding is enabled for this KPI.
sec_grpStringThe team the object belongs to. This object can only belong to default_itsi_security_group (Global team).

KPI Base Search

Description

Searches that can be aggregated together to reduce overall search load. KPI Base Searches include the core attributes of a KPI for search generation.

kpi_base_search objects are contained within the KPI (kpis) object data structure.

Attributes

FieldTypeDescription
entity_alias_filtering_fieldsStringThe fields to filter on. See KPI definition.
_versionStringITSI version number of this KPI base search.
descriptionStringGeneral description for this KPI base search.
mod_sourceStringSource of the last modification.
mod_timeStringThe time of the last modification based on UTC time zone.
is_service_entity_filterBooleanIf true a filter is used on the search based on the entities included in the service.
actionsString
object_typeStringkpi_base_search
is_entity_breakdownStringDetermines if search breaks down by entities. See KPI definition.
_ownerStringKV store owner.
source_itsi_daStringSource of DA used for this search. See KPI Threshold Templates.
metricsArraySet of statistical operations performed on threshold field.
aggregate_statopStringStatistical operation (avg, max, median, stdev, and so on) used to combine data for the aggregate alert_value (used for all KPI).
unitStringUser-defined units for the values in threshold field.
titleStringName of this metric
_keyStringInternal identifier.
threshold_fieldStringThe field on which the statistical operation runs.
entity_statopStringStatistical operation (avg, max, mean, and so on) used to combine data for alert_values on a per entity basis (used if is_entity_breakdown is true).
search_alert_earliestStringEarliest time to look for events every time KPI search runs. This determines how far back each time window is during KPI search runs.
alert_periodStringUser specified interval to run the KPI search in minutes.
alert_lagStringContains the number of seconds of lag to apply to the alert search, max is 30 minutes (1800 seconds).
base_searchStringKPI search defined by user for this KPI. All generated searches for the KPI are based on this search.
entity_id_fieldsStringFields from this KPI's search events that will be mapped to the alias fields defined in entities for the service containing this KPI. This field enables the KPI search to tie the aliases of entities to the fields from the KPI events in identifying entities at search time.
identifying_nameStringInternal only
titleStringName of this KPI base search.
mod_timestampStringTimestamp of last modification based on UTC time zone.
aclStringAccess control blob.
_userStringLike owner, but different.
_keyStringAuto-generated unique ID for this KPI.
sec_grpStringThe team the object belongs to. This object can only belong to default_itsi_security_group (Global team).

For more information, see Create KPI base searches in ITSI in the Service Insights Manual.

Glass Table

Description

ITSI glass tables are custom visualizations that let you monitor KPI search results.

glass_table objects define all widgets and drawing elements that appear in the glass table.

Attributes

FieldTypeDescription
_keyStringUnique identifier for this glass table.
titleStringName of this glass table.
descriptionStringUser-defined description for this glass table.
object_typeStringglass_table.
latestStringLatest time for all of the widget searches on the glass table.
latest_labelStringLatest label displayed in the glass table instant picker. Matches latest attribute.
svg_coordinatesStringx and y viewbox offsets for the glass table.
contentArrayArray of JSON structures containing all attributes needed to draw the glass table. See Glass Table Widget Configuration.
is_epochBooleanTrue when the glass table uses a custom (non-preset) time, false otherwise.
templateSelectedServiceIdStringThe id of the service currently in focus if templatization is enabled.
templateSwappableServiceIdsArrayThe array of services available to be swapped to for templatization.

Subordinate data structures

  • Glass Table Widget Configuration
  • Glass Table Icon

Glass Table Widget Configuration

Description

Glass Table Widget Configuration (content) is an array of JSON structures that contains all of the attributes needed to render the glass table. Each element of the array represents one glass table widget, and the attributes of the element are parsed into a glass table BaseWidgetViewManager object.

Attributes

FieldTypeDescription
searchStringThe search to power the widget.
labelValStringThe text to show in the label located beneath the widget.
labelFlagBooleanTrue if labelVal is to be shown with the widget, false otherwise.
vizTypeIntegerNumeric indication of which visualization type the widget is - SingleValue, Gauge, Sparkline, SVD from 0-3, respectively
threshold_fieldStringField in data to which thresholds apply.
threshold_comparatorStringComparator used for threshold severity computation
threshold_valuesArrayArray of values to indicate the bounds of the thresholds set for the widget.
threshold_labelsArrayArray of labels to match the threshold values set for the widget.
context_idStringId of service to which the widget's KPI belongs.
kpi_idStringId of KPI the widget represents
searchSourceStringSource of search for glass table widget - can be datamodel or ad hoc.
dataModelSpecificationStringData model specification for the datamodel search.
dataModelStatOpStringDatamodel stats operation for the datamodel search.
dataModelWhereClauseStringDatamodel where clause for the datamodel search.
threshold_evalStringThreshold eval search clause for threshold severity evaluation.
aggregate_evalStringAggregate eval search clause for threshold severity evaluation.
base_searchStringBase search of the KPI the widget represents.
search_alert_earliestStringEarliest time for the search that powers the widget.
entitiesStringList of entities that the widget's KPI contains.
search_aggregateStringAggregate search of the KPI the widget represents.
search_time_series_aggregateStringTime series search of the KPI the widget represents
search_time_compareStringCompare time series search of the KPI the widget represents (for the SVD viz type).
search_typeStringType of search the widget is powered by. Must match one of the search_* attributes of the widget.
relativeEarliestStringEarliest time (in relative units) for the search that powers the widget.
defaultWidthIntegerInitial width to use for the widget.
defaultHeightIntegerInitial height to use for the widget.
existingKPIBooleanTrue if KPI exists in user's system, false otherwise.
alert_onStringThreshold alert type (aggregate or entities) of the KPI the widget represents.
isThresholdEnabledBooleanTrue if thresholds should be applied to the widget's search results, false otherwise.
useKPISummaryBooleantrue if widget uses the kpi_summary_index to power its search, false otherwise.
unitStringUnit string for widget to display.
gap_severityStringGap severity value of the KPI the widget represents.
gap_severity_colorStringGap severity color of the KPI the widget represents.
drilldownSettingsModelStringModel to hold properties required for generating URLs for custom drilldown.
useCustomDrilldownBooleanTrue if widget has custom drilldown turned on, false otherwise.

Glass Table Icon

Description

Contains SVG icon definitions and metadata for glass table icons.

Attributes

FieldTypeDescription
_keyStringAuto-generated unique identifier for this icon.
titleStringName of the icon.
categoryStringCategory of the icon.
default_widthIntegerWidth of the icon.
default_heightIntegerHeight of the icon.
svg_pathStringSVG path defining shape of the icon.
immutableBooleanShould the REST API allow editing of this icon. False for all icons imported from .conf files.
_timeStringTimestamp when the icon was added.
_ownerStringName of the user that added this icon.

Deep Dive

Description

ITSI deep dives are investigative tools that help you identify and troubleshoot issues in your IT environment. You can use deep dives to view KPI search results over time, zoom-in on KPI metrics and log events, and visually correlate root cause. You can add different types of lanes to a deep dive view, including KPI lanes, which let you view KPI metrics in detail. You can also add lanes to view ad hoc and data model searches.

deep_dive objects contain all of the elements required to render deep dive lanes.

Attributes

FieldTypeDescription
_keyStringAuto-generated unique identifier for this deep dive.
descriptionStringUser-defined description for this deep dive.
titleStringName of the deep dive.
object_typeStringdeep_dive
earliest_timeStringEarliest time for all of the searches in this deep dive.
latest_timeStringLatest time for all of the searches in this deep dive.
focus_idStringThe service id of the service in focus.
topology_idStringDefine the service to be put in focus in the deep dive topology view. If none exists then the focus_id is set as the topology_id. view sidebar
lane_settings_collectionArray<Array of lane settings specifying each lane's configuration. See Deep Dive Lane Settings.
is_namedBooleanTrue when the deep dive is saved, false otherwise.

Subordinate data structures

  • Deep Dive Lane Setting

Deep Dive Lane Setting

Description

Configuration settings that define what information a deep dive lane shows. Deep dive views use these settings for per lane configuration.

Attributes

FieldTypeDescription
titleStringName of the lane to display.
subtitleStringThe subtitle of the lane to display.
laneTypeStringThe type of lane to render. Possible values: event, kpi, metric (the default).
graphTypeStringThe type of graph to render
searchStringThe search to use to get data for the lane.
searchSourceStringRepresents how a search is generated. Possible values: datamodel, ad hoc search, or kpi search.
dataModelSpecificationObjectAn object showing the selections that went into the generation of the search, null unless searchSource is data model. If defined, it is structured as {datamodel: <Data Model name> object: <Object Name>, field: <Field Info Data Structure>.
dataModelStatOpStringStats operation used in the data model search.
dataModelWhereClauseStringWhere clause defined during data model search creation.
overwriteKpiTitleStringOverwrite KPI title with user specified title.
overwriteEntityTitleStringOverwrite Entity title with user specified title.
kpiTitleStringThe original title of the KPI as defined in the KPI model.
kpiServiceIdStringThe id of the service associated with the selected KPI.
kpiUnitStringThe unit of the KPI driving this lane.
kpiAddToSummaryStringAdd or remove from kpi summary based on user selection. [yes, no] Yes runs the search against kpi summary index and no runs raw search.
kpiStatsOpStringStats operation to calculate the KPI value, avg by default [avg, max, min, median].
entityAddToSummaryStringShows the accelerated output for entity lanes. Always set to "yes."
thresholdIndicationEnabledStringEnable/disable threshold indication. Disabled by default.
thresholdIndicationTypeStringType of threshold indication. [foreground/background] Foreground selected by default.
hideGraphStringOnly available with background threshold indications. If selected, hides the graph and only shows the top view with background thresholds [yes, no].
verticalAxisScaleStringDetermines the scale of the y axis. It is linear or log.
verticalAxisBoundaryTypeStringDetermine the extent of the y axis. It is staticValue, value, or zeroValue.
verticalAxisStaticBoundsObjectIf static, these are the bounds to use. Otherwise this is ignored. This is an object of the form[<min number>, <max number>].
dataGapsStringnull values in the data can be represented as gaps or connected through the graph.
graphColorStringThe color of the graph to render.
graphSeriesStringThe field in the data which to plot as the range, if unspecified plots all.
excludeSeriesStringThe series of data to omit from being displayed in graph. Series with a leading _ (indicating internal use) is always excluded.
laneOverlaySettingsModelObjectModel to define the overlay lane settings.

Time Variate Thresholds Specification

Description

This data structure contains the threshold policy collection. A threshold policy includes information on which thresholds are to be applied (a threshold setting model), how those thresholds are generated, and the time periods to which the threshold policy applies. Each policy object includes a single time_blocks attribute that contains a list of time periods with which the policy is associated.

In the case of static thresholding there are no parameter attributes. In the case of dynamic thresholding, parameters are stored in a simple object within the policy.

Attributes

FieldTypeDescription
titleStringThe title of the threshold spec. Used when creating/modifying threshold spec templates.
descriptionStringUser-defined description of the threshold specifications.
policiesObjectJSON object keyed by policy ID.
time_blocksArrayDetermines time periods with which the policy is associated.

Collection details

A threshold policy collection is accessed by the UUID key of the policy. There is no limit to the number of policies a collection can contain.

Threshold policies

{ _key: <UUID>, title: <optional title>, aggregate_thresholds: <ThresholdSettingsModel>, entity_thresholds: <ThresholdSettingsModel>, policy_type: <ENUM of "static", "stdev", "quantile", or "range"> time_blocks: <[] of time blocks>}

Time blocks attribute

The time_blocks attribute uses a simplified cron expression format:

[ ['<minute> <hour> <*> <*> <day>', <duration in minutes>] ]

<minute> values can only be 0, 15, 30, or 45. <hour> values use 24 hour day format. Unlike standard cron expressions, <day> values run from 0 (Monday) through 6 (Sunday).

For example:

'time_blocks': [ ['15 3 * * 3,4', 60] // 1 hour time range, 3:15AM - 4:15AM on Thurs, Fri]

The time block attribute must specify exactly one cron expression.

If your existing configuration doesn't match the UTC timestamp, use the kvstore_to_json.py script to correct the time zone discrepancy. See Time zone offset operations (mode 3) in the Administration Manual.

Usage

Generation of Time Varied Threshold lookup in custom search command

The main usage of the threshold policy structures is to determine which thresholds should be applied based on the time.

Configure adaptive threshold commands

Threshold policy structures are used to configure how the adaptive threshold commands work. They need access to the time blocks for a particular policy and the parameters in the policy. They access this information by reading the KPI and applying the information stored within.

Maintenance Calendar

Description

Use maintenance_calendar to put services and entities in maintenance mode at required intervals.

Attributes

FieldTypeDescription
_keyStringUnique ID for the entry in the KV store.
titleStringTitle of the maintenance window.
commentStringOptional description of the maintenance window.
objectsArrayArray of dictionaries describing the objects put in maintenance by this maintenance window.
The schema for each object definition in the array:
_key: Unique if assigned to the object currently.
object_type: Type of object being identified. Currently only entity and service are supported.
start_timeStringTimestamp that marks the beginning of maintenance window. Based on UTC time.
end_timeStringTimestamp that marks the end of maintenance window. Based on UTC time.

If your existing configuration doesn't match the UTC timestamp, use the kvstore_to_json.py script to correct the time zone discrepancy. See kvstore_to_json.py operations in ITSI in the Administration Manual.

Event Management State

Description

The event_management_state object stores user settings for custom saved views of Episode Review. For instructions to save custom views through the UI, see Save a custom view of Episode Review in the User Manual.

Attributes

FieldTypeDescription
_keyStringThe unique ID for Episode Review view in the KV store.
titleStringA user-defined name for the custom episode review.
earliestStringThe earliest time for the main search in the Episode Review custom view.
latestStringThe latest time for the main search in the Episode Review custom view.
fetchLimitIntegerThe maximum number of notable events to fetch in a single request.
sortFieldStringThe field in the data (column in Episode Review) to sort notable events by.
sortDirectionStringWhether to sort notable events in ascending or descending order.
arbitrarySearchStringThe Splunk search string used to filter raw notable events.
filterCollectionArrayA set of filters that represent the Episode Review page filters.
viewingOptionStringWhether to display notable events as standard or prominent mode in Episode Review.
eventDeduplicationBooleanIf true, episode view is turned on. Otherwise individual notable events are displayed.
columnsShownArrayA list of fields in the data (columns in Episode Review) to display.

Notable Event Group

Description

The notable_event_group contains information about an episode.

Attributes

FieldTypeDescription
severityStringThe level of importance of the episode. Values must match an integer specified in the default version of itsi_notable_event_severity.conf (or the local version if you created one). Default values:
1 - Info
2 - Normal
3 - Low
4 - Medium
5 - High
6 - Critical
statusStringThe triage status of the episode in Episode Review. Values must match an integer specified in the default version of itsi_notable_event_status.conf (or the local version if you created one). Default values:
0 - Unassigned
1 - New
2 - In Progress
3 - Pending
4 - Resolved
5 - Closed
ownerStringThe Splunk user who is the owner of the episode.
_keyStringThe episode ID that a change is associated with.

Notable Event Comment

Description

notable_event_comment contains comments associated with an episode.

Attributes

FieldTypeDescription
commentStringThe text of the comment.
event_idStringThe episode ID that the comment is associated with.
is_groupBooleanThe episode ID that the comment is associated with.
filter_searchStringThe search to retrieve all the comments for an episode.
earliest_timeStringThe time, in UTC, of the first event in the episode.
latest_timeStringThe time, in UTC, of the last event in the episode.

Notable Event Aggregation Policy

Description

notable_event_aggregation_policy contains the data for a notable event aggregation policy which aggregates notable events into episodes.

Attributes

FieldTypeDescription
disabledBoolean1 if the aggregation policy is disabled and 0 if enabled.
breaking_criteriaObjectA JSON blob of all the criteria used to break an episode.
filter_criteriaObjectA JSON blob of all the criteria used to filter events into an episode.
is_defaultBooleanIndicates if this is the default aggregation policy. 1 if it's the default policy and 0 if not.
descriptionStringThe description of the notable event aggregation policy.
group_severityStringThe default severity of each episode created by the notable event aggregation policy.
group_statusStringThe default status of each episode created by the notable event aggregation policy.
group_asigneeStringThe default owner of each episode created by the notable event aggregation policy.
group_descriptionStringThe default description of each episode created by the notable event aggregation policy.
titleStringThe title of the notable event aggregation policy.
rulesArrayAn array of all the rules and actions to be executed for the notable event aggregation policy.
split_by_fieldStringA string containing all the fields to split episodes by.

Notable Event Email Template

Description

notable_event_email_template contains the data for email templates for episode actions. Once you create a template it's available for selection in all aggregation policies and is not policy-specific.

Attributes

FieldTypeDescription
titleStringThe name of the message template. This element is required.
messageStringThe body of the email. Supports tokens such as $result.title$ and $result.description$. This element is required.

Correlation Search

Description

correlation_search contains the data for a correlation search. A correlation search is a recurring search that generates a notable event when search results meet specific conditions. A multi-KPI alert is a type of correlation search.

Attributes

FieldTypeDescription
is_scheduledIntegerValues: 1 means scheduled; 0 means not scheduled.
disabledIntegerValues: 1 means disabled; 0 means enabled.
cron_scheduleStringSchedule searches to run periodically at fixed times, dates, or intervals using a cron expression. Default value is */5* * * * (every 5 minutes).
dispatch.earliest_timeStringIndicates the beginning of the time range for the search. The default value is -15m.
dispatch.latest_timeStringIndicates the end of the time range for the search. The default value is -now.
descriptionStringA description of the type of issue the search is intended to detect.
searchStringThe Splunk search to run.
nameStringA name that describes the correlation search. For example, "cpu_load_percent".
action.itsi_event_generator.param.titleStringThe title to use for the notable event in Episode Review. For example, mysql-01 server cpu Load%.
action.itsi_event_generator.param.descriptionStringA brief phrase to describe the notable event. For example, "This alert triggers when DB CPU load on the mysql-01 server reaches 80%."
action.itsi_event_generator.param.statusStringThe triage status of the event in Episode Review. You can provide a token in the format %fieldname% to substitute the value of a third-party alert field. Values must match an integer specified in $SPLUNK_HOME/etc/apps/SA-ITOA/local/itsi_notable_event_status.conf or /default/itsi_notable_event_status.conf if a local version does not exist. By default, these values are 0-5.
action.itsi_event_generator.param.ownerArrayThe ITSI role to which the notable event is assigned in Episode Review.
action.itsi_event_generator.param.severityStringThe level of importance of the event. You can provide a token in the format %fieldname% to substitute the value of a third-party alert field. Values must match an integer specified in $SPLUNK_HOME/etc/apps/SA-ITOA/local/itsi_notable_event_severity.conf or /default/itsi_notable_event_severity.conf if a local version does not exist. By default, these values are 1-6.
action.itsi_event_generator.param.drilldown_search_titleStringThe name of the drilldown search link. You can drill down to a specific Splunk search from an episode in Episode Review.
action.itsi_event_generator.param.drilldown_search_searchStringThe Splunk search you drill down to.
action.itsi_event_generator.param.drilldown_search_latest_offsetStringDefines how far ahead from the time of the event to look for related events.
action.itsi_event_generator.param.drilldown_search_earliest_offsetStringDefines how far back from the time of the event to start looking for related events.
action.itsi_event_generator.param.drilldown_titleStringThe name of the drilldown website link if you want to drill down to a specific website from the episode in Episode Review.
action.itsi_event_generator.param.drilldown_uriStringThe website you drill down to.
action.itsi_event_generator.param.event_identifier_fieldsStringThese identifier fields form the event hash field, which is added to every notable event to help identify unique alarm types.
action.itsi_event_generator.param.service_idsStringOne or more ITSI services to which this correlation search applies. You can only specify services that belong to teams for which you have read access.
action.itsi_event_generator.param.entity_lookup_fieldStringThe field in the data retrieved by the correlation search that is used to look up corresponding entities. For example, host.
action.itsi_event_generator.param.search_typeStringsearch_type = "basic", "composite_kpi_score_type", or composite_kpi_percentage_type
action.itsi_event_generator.param.meta_dataObjectOne of two JSON object schemas, depending on whether it is a correlation search or a multi-KPI alert.
Correlation search object schema:
  • threshold_health_score - threshold score set by user
  • threshold_status - threshold status (default is undefined)
  • suppression criteria fields
  • alert_type - score or status
  • is_suppression - if suppression is enabled or not
  • is_consecutive - if count is consecutive or not
  • count - minimum number of times if this alert happens
  • suppression_period - suppression period in minute if it is non-consecutive
  • min_alert_period - minimum alert period of selected KPIs
  • run_every - frequency of search in minutes
  • score_based_kpis - list of KPIs which is added as part of a composite KPI. Each object in the list must have kpiid - <kpi id>, serviceid - <service id>, urgency - <urgency value>

Multi-KPI alert object schema:

  • time_label - time label for time range
  • percentage_based_kpis - list of KPIs and service IDs included. Each item should contain kpiid - <kpi id>, serviceid - <service id>, label_thresholds - <threshold and operation type for trigger>. label_thresholds data format is as follows:

{operation: 'OR', // default for now thresholds: [{severity: <severity name>,percentage: <percentage value>,percentage_operation: '>=', // default for now} ......]}

action.itsi_event_generator.param.editorStringOne of two values: advance_correlation_builder_editor or multi_kpi_alert_editor. It directs to the specific UI page to make edits based on the type of search, correlation search or multi-KPI alert.
action.itsi_event_generatorIntegerValue: 1
actionsStringValue: itsi_event_generator
alert.suppressIntegerEnable suppression to minimize the number of duplicate notable events sent to Episode Review. Values: 1 (means enabled) or 0 (means disabled).
alert.suppress.fieldsStringThe fields to consider when determining if another event matches the current one.
alert.suppress.periodStringThe number of seconds to ignore other events that have the same field values.
action.rssIntegerIncluded in RSS feed. Values: 1 (means enabled) or 0 (means disabled).
action.emailIntegerSend an email when the alert is triggered. Values: 1 (means enabled) or 0 (means disabled).
action.email.toStringThe email addresses to send the email to.
action.email.subjectStringThe subject of the email.
action.email.sendcsvIntegerSend an email in CSV format. Values: 1 (means enabled) or 0 (means disabled).
action.email.sendpdfIntegerSend an email with a PDF attachment. Values: 1 (means enabled) or 0 (means disabled).
action.email.inlineIntegerSend an email with the text inline. Values: 1 (means enabled) or 0 (means disabled).
action.email.formatStringDefault value is pdf. Other values: html, csv.
action.email.sendresultsStringInclude alert information as an email attachment. Values: 1 (means enabled) or 0 (means disabled).
action.scriptIntegerTriggers a shell script if enabled. Values: 1 (means enabled) or 0 (means disabled).
action.script.filenameStringProvide the file name of the shell script to run when this alert is triggered.

Service Analyzer

Description

Service Analyzer is the ITSI UI home page. It displays service and KPI health scores that are trending at top severity levels. You can configure Service Analyzer to filter the display of services and KPIs relevant to the user.

The Service Analyzer object is called home_view.

Attributes

FieldTypeDescription
_keyStringUnique ID for the entry in KV store.
object_typeStringhome_view
-ownerStringUser that creates the saved service analyzer.
titleStringUser given title for the service analyzer.
earliest_timeStringEarliest time for the searches.
latest_timeStringLatest time for the searches.
serviceWhitelistStringList of filtered services.
kpiWhitelistStringList of filtered kpis.
isServiceFilterEnabledBooleanTrue if services are filtered, false by default.
isKpiFilterEnabledStringTrue if kpis are filtered, false by default.
serviceTilesSettingsObjectSeverityTilesSettingModel with number of kpi tiles and filter.
viewStringDetermines if service analyzer view is standard or full screen. Standard is default.
isDefaultStringTrue if it is the default (standard) service analyzer, false otherwise.
titleSizeStringmedium|large], large by default.
searchTypeStringmaxseverity] [aggregate|maxseverity] aggregate shows the most recent service value and the max severity is service value unless there is an entity value with worst severity.

Team

Description

Teams are used to restrict service-level information in the following objects:

  • Glass tables
  • Service analyzers
  • Deep dives
  • Episode Review
  • Correlation searches
  • Multi-KPI alerts

The team object is called team.

Attributes

FieldTypeDescription
identifying_nameStringThe name of the team. Does not have to match title.
aclStringAccess control list for the team. Must include itoa_admin.
titleStringUser provided name of the team. Does not have to match identifying_name.
descriptionStringUser provided description of the team.
childrenListList of private teams created in ITSI. For private teams, this field will be an empty list.
parentsListThe parent of this team. Cannot be configured in current release.
_keyStringUnique ID for the entry in KV store.

Anomaly Detection Algorithm Settings

Attributes

FieldTypeDescription
SensitivityIntegerDetermines sensitivity of algorithm to variance in data. Note that acceptable values for both trending and cohesive algorithm sensitivity are between 0 and the sensitivity_max parameter value, as specified in the respective [trending:limits]and [cohesive:limits] stanzas, in mad.conf in the SA-ITSI-MetricAD namespace.

Event Management Export

Description

itsi_event_management_export contains information about an episode.

Attributes

FieldTypeDescription
export_filenameStringThe file name for the new file export.
object_typeStringevent_management_export
statusStringThe status of the CSV file export: started, in progress, failed, completed.
_ownerStringThe Splunk user who owns the CSV file.
_keyStringA unique identifier to determine the CSV file object.
ITSI REST API schema - Splunk Documentation (2024)
Top Articles
Latest Posts
Article information

Author: Laurine Ryan

Last Updated:

Views: 5404

Rating: 4.7 / 5 (57 voted)

Reviews: 80% of readers found this page helpful

Author information

Name: Laurine Ryan

Birthday: 1994-12-23

Address: Suite 751 871 Lissette Throughway, West Kittie, NH 41603

Phone: +2366831109631

Job: Sales Producer

Hobby: Creative writing, Motor sports, Do it yourself, Skateboarding, Coffee roasting, Calligraphy, Stand-up comedy

Introduction: My name is Laurine Ryan, I am a adorable, fair, graceful, spotless, gorgeous, homely, cooperative person who loves writing and wants to share my knowledge and understanding with you.