The integration comprises three connectors, targeted at different data transfer scenarios:
Splunk 4, 5, 6.
The "Moviri Integrator for BMC TrueSight Capacity Optimization – Splunk (Unix and Windows)" connector requires:
The "Moviri Integrator for BMC TrueSight Capacity Optimization – Splunk (Web Logs)" connector requires:
ETL Modules are made available in the form of an additional components, which you may download from BMC electronic distribution site (EPD) or retrieve from your content media.
To install the connector in the form of a TrueSight Capacity Optimization additional package, refer to Performing system maintenance tasks instructions.
All the connectors included in "Moviri Integrator for BMC TrueSight Capacity Optimization – Splunk" use the Splunk REST API to communicate with Splunk. This is always enabled and no additional configuration is required, even Splunk Web and the Splunk CLI use Splunk's REST API to communicate with a Splunk instance.
The connector requires a user with the following roles:
The following are the common settings valid for all connectors of "Moviri Integrator for TrueSight Capacity Optimization - Splunk", they are presented in the "Splunk - Setting" configuration tab.
The web address where the Splunk instance can be reached
The Management port of the Splunk instance where the REST API can be contacted.
Select the Splunk application in which the search will be executed, if not set, the user's default application will be used
Default last counter
Date and time to extract the extraction from, in case of first execution.
Max days to extract
Maximum number of days' worth of data to extract in a single execution. Set 0 for no limitations.
The granularity of the extracted data. For "Moviri – Splunk Generic Extractor" it must match the granularity resulting from the search query execution.
See further specific instructions for each extractor: