Hardware and software requirements for the Splunk Add-on for BMC Remedy

Splunk admin requirements

To install and configure the Splunk Add-on for BMC Remedy, you must have the admin or sc_admin role. To use the custom commands that enable push integration with Remedy, you must have the admin_all_object capability in the Splunk platform.

Remedy setup requirements

Remedy account permissions

You must have a Remedy account with Incident User permissions in order to set up integration with the Splunk platform. The Splunk platform uses this account to create and modify Remedy incidents from the Splunk platform.

Data Collection requirements

Based on your requirements, you must provide appropriate permissions to the user configured via the REST account for data collection.

See the BMC Remedy documentation to view different permissions and allowed operations.

Set the Consolidating Incidents option to No

For triggered alerts to successfully create new incidents for configuration items, you must configure incident rules and set the Consolidate Incidents option to No in BMC Remedy IT Service Management (ITSM). For information about configuring the Consolidate Incidents setting in the Remedy, refer to the related Remedy documentation:
https://docs.bmc.com/docs/display/public/BSR35/Consolidating+incidents

Splunk platform requirements

Because this add-on runs on the Splunk platform, all of the system requirements apply for the Splunk software that you use to run this add-on.

• For Splunk Enterprise system requirements, see System Requirements in the Splunk Enterprise Installation Manual.
• If you are managing on-premises forwarders to get data into Splunk Cloud, see System Requirements in the Splunk Enterprise Installation Manual, which includes information about forwarders.