What should be considered when onboarding data into a Splunk index, assuming that ITSI will need to use this data?

Question

Options

• AUse | stats functions in custom fields to prepare the data for KPI calculations.
• BCheck if the data could leverage pre-built KPIs from modules, then use the correct TA to
• CMake sure that all fields conform to CIM, then use the corresponding module to import related
• DPlan to build as many data models as possible for ITSI to leverage

• A
  4% (2)
• B
  74% (40)
• C
  9% (5)
• D
  13% (7)

Explanation

When onboarding data into a Splunk index, assuming that ITSI will need to use this data, you should consider the following: onboard the data. This is true because modules are pre-packaged sets of services, KPIs, and dashboards that are designed for specific types of data sources, such as operating systems, databases, web servers, and so on. Modules help you quickly set up and monitor your IT services using best practices and industry standards. To use modules, you need to install and configure the correct technical add-ons (TAs) that extract and normalize the data fields required by the

No community discussion yet for this question.