Splunk® Supported Add-ons

Splunk Add-on for BMC Remedy

Acrobat logo Download manual as PDF

Acrobat logo Download topic as PDF

Set up the Splunk Add-on for BMC Remedy

Follow these steps to set up the add-on using the setup screen in the App Manager. You need to know the user name and password for an account with Incident User permissions on your Remedy system for creating incidents and the modifying incidents in your Remedy environment to perform the setup.

If your Splunk platform deployment is distributed, you need to perform the setup steps on your search heads. If you are using this add-on with a search head cluster (supported for Splunk platform 6.3.x or later), perform these setup steps on one search head node. The cluster will sync the credentials to your other nodes automatically. Before you begin, click ''Settings > Show All Settings'' so that you can see the Setup link on your search head cluster node.

  1. In Splunk Web, click on the Splunk Add-on for BMC Remedy icon in the Apps sidebar to launch the add-on.
  2. Click on the Configuration button.
  3. Click on the Account tab to configure Remedy server information. See the steps below for more information.
  4. If using a proxy, click on the Proxy tab to configure proxy settings. See the steps below for more information.
  5. Click on the Logging tab to configure logging levels. See the steps below for more information.

Configure Account settings

  1. In Splunk Web, click on the Splunk Add-on for BMC Remedy icon in the Apps sidebar to launch the add-on.
  2. Click the Account tab to navigate to the Splunk Add-on for BMC Remedy account configuration settings.
  3. In the Account tab, enter the full URL of the Remedy server in the Remedy Server URL field. The AR System Server information can be found in the BMC Remedy AR System Administration Console, under General > Server Information.
  4. In the AR System Server field, enter the hostname of the Remedy AR system server.
    The AR System Server information can be found in the BMC Remedy AR System Administration Console, under General > Server Information.
  5. Enter the User name and Password for the account on your Remedy system and confirm the password.

    Password is not a mandatory field, as Remedy Server allows accounts without passwords.

  6. Click Save.

Configure Proxy settings

Configure a proxy connection to your remedy server.


  1. In Splunk Web, click on the Splunk Add-on for BMC Remedy icon in the Apps sidebar to launch the add-on.
  2. Click the Proxy tab to navigate to the Splunk Add-on for BMC Remedy proxy configuration settings.
  3. Click Enable Proxy.
  4. Select the type of proxy to use in the Proxy Type field.
  5. Enter the proxy server address in the Host field.
  6. Enter the proxy server port in the Port field. For example, 8081.
  7. Enter a proxy username (if you have one) in the Username field, and enter the proxy password in the Password field. The Splunk platform encrypts the proxy username and password as soon as you enter these values.
  8. Click the Reverse DNS resolution box if you want to perform DNS resolutions through your proxy.
  9. Click Save.

If, you want to disable your proxy but save your configuration, repeat steps 1 and 2 above, and uncheck the Enable Proxy box. The Splunk Add-on for BMC Remedy stores your proxy configuration so you can enable it again later. To delete your proxy configuration, delete the values in the fields.

Configure Logging settings

  1. In Splunk Web, click on the Splunk Add-on for BMC Remedy icon in the Apps sidebar to launch the add-on.
  2. Click the Logging tab to adjust logging level. The data collection Logging level defaults to INFO. Verbosity increases in the following order: ERROR, WARN, INFO, DEBUG, CRITICAL. If you experience issues with the add-on, enable "DEBUG" level logging to help troubleshoot.
  3. Click Save.

If you have more than one search head, perform the same steps on each search head to support search-time push integration.

If the Remedy service definition changes after you have set up the add-on, you will need to perform the add-on setup again.

Switch between encrypted and unencrypted communication

By default, all the communications from the Splunk Add-on for BMC Remedy to your Remedy servers will be encrypted via HTTPS with SSL certificate validation enabled. If your Remedy server is configured with HTTPS and a valid CA signed certificate, then the communication to Remedy server work with default configurations.

If your Remedy server is configured with HTTPS using a self signed certificate, follow the below steps.

  1. Download the intermediate CA certificate of the Remedy server certificate in PEM format.
  2. Place the CA certificate in the local folder of the Splunk Add-on for BMC Remedy.
  3. Provide the path of the CA certificate file in $SPLUNK_HOME/etc/apps/Splunk_TA_remedy/default/splunk_ta_remedy_settings.conf under the additional_parameters stanza.
  4. Save your changes.

If your Remedy server is not configured with HTTPS and only supports HTTP communications, follow the below steps.

  1. Change the value of the http_scheme field to HTTP instead of HTTPS in $SPLUNK_HOME/etc/apps/Splunk_TA_remedy/default/splunk_ta_remedy_settings.conf file under the additional_parameters stanza.
  2. Enter the server_url field according to HTTP or HTTPS in $SPLUNK_HOME/etc/apps/Splunk_TA_remedy/default/splunk_ta_remedy_settings.conf file under the additional_parameters stanza.
  3. Save your changes.

If the Remedy service definition changes after you have set up the add-on, you will need to perform the add-on setup again.

If you are configuring the add-on on a search head and if you have more than one search head in cluster, perform the same steps for all the above sections on each search head to support search-time push integration.

Last modified on 09 July, 2020
PREVIOUS
Upgrade the Splunk Add-on for BMC Remedy
  NEXT
Specify required fields for incidents for the Splunk Add-on for BMC Remedy

This documentation applies to the following versions of Splunk® Supported Add-ons: released, released, released


Was this documentation topic helpful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters