What are valid considerations when designing an ITSI Service? (Choose all that apply.)

The correct answer is A. Service access control requirements for ITSI Team Access should be considered, and B. Entities, entity meta-data, and entity rules should be planned carefully to support the service C. Services, entities, and saved searches are stored in the ITSI app, while events created by KPI. A, B, and C are correct answers because service access control requirements for ITSI Team Access should be considered before creating the ITSI Service, as different teams may have different permissions and views of the service data. Entities, entity meta-data, and entity rules sh

Splunk ITSI Concepts and Environment

Question

Options

AService access control requirements for ITSI Team Access should be considered, and
BEntities, entity meta-data, and entity rules should be planned carefully to support the service
CServices, entities, and saved searches are stored in the ITSI app, while events created by KPI
DBackfill of a KPI should always be selected so historical data points can be used immediately and

How the community answered

(36 responses)

A
81% (29)
D
19% (7)

Explanation

A, B, and C are correct answers because service access control requirements for ITSI Team Access should be considered before creating the ITSI Service, as different teams may have different permissions and views of the service data. Entities, entity meta-data, and entity rules should also be planned carefully to support the service design and configuration, as they determine how ITSI maps data sources to services and KPIs. Services, entities, and saved searches are stored in the ITSI app, while events created by KPI execution are stored in the itsi_summary index for faster retrieval and analysis.

Topics

#service design#entities#access control#KPI backfill

Community Discussion

No community discussion yet for this question.

Full SPLK-3002 Practice