Monitoring Splunk Connectivity to JSD Server



You can check the status of your Splunk server connections on the JIRA Service Desk (JSD) configuration page for the add-on. You can also see any issues that have failed to send in real time, and either resend them or remove them from the queue. You have the option to monitor Splunk connectivity and receive failure notifications in HipChat (requires the HipChat integration). The settings for these connectivity checks are configurable.

Prerequisites

Checking Splunk Connectivity in JSD

The add-on automatically checks the connectivity of your Splunk servers every 2 minutes, by default. You can view the current status of these checks on the JSD configuration page for the add-on.

  1. Click the gear icon, and then click Applications.
  2. Under Integrations, click RealTime Splunk Connector for JIRA.

  3. Click the Splunk Servers tab.
    For each server, the table shows the results of the most recent connectivity check and the reason for a failure, if applicable.
  4. To modify or remove a Splunk server connection, click the ellipses, and then click Edit or Delete.

    The add-on verifies the Splunk URL before activating the connection. If you receive an error message about the Splunk URL, correct the settings and then activate the Splunk server.

     

    Refreshing the list

    To retry the connection and update the page with the latest status, click the Refresh icon ().

Viewing Unsent Issues

The add-on sends JSD data to the Splunk servers in real time, when an issue event triggers it. If a connectivity issue prevents an issue from being sent successfully, the add-on stores the issue in a queue and periodically attempts to resend it. You can review the issues in this queue and either try to resend them or remove them from the queue.

  1. Click the gear icon, and then click Applications.
  2. Under Integrations, click RealTime Splunk Connector for JIRA.

  3. Click the Splunk Servers tab.
  4. Click the ellipses beside a Splunk server, and then click View Unsent Issues.
    The table lists the JSD issues that haven’t been successfully sent to Splunk with a reason for the failure.


  5. To view the data payload for an unsent issue, click the ellipses, and then click View Issue Details.
  6. To resend or permanently remove the issue from the queue, click the ellipses, and then click Resend or Delete.

    Refreshing the list

    To retry the connection and update the page with the latest status, click the Refresh icon ().

Monitoring Splunk Connectivity with HipChat

You can monitor Splunk connectivity and receive failure notifications in HipChat.

After you install the HipChat integration for a room, the right sidebar shows a summary of the connectivity status between JSD and your Splunk servers. You can click the summary to expand details for each Splunk server.

The add-on sends a notification to HipChat if a Splunk server fails 5 consecutive connectivity checks, by default. You can click the card title to go directly to the Splunk Servers tab in JSD.

Changing the Settings for Connectivity Checks

You can change the default values for the frequency of connectivity checks, when to send a HipChat notification, and other communication settings between JSD and Splunk.

  1. Click the gear icon, and then click Applications.
  2. Under Integrations, click RealTime Splunk Connector for JIRA.

  3. Click Settings.
  4. On the Settings page, configure the communication settings between JSD and Splunk.

    FieldDescription
    Splunk Heartbeat IntervalHow often the add-on checks the connectivity of your Splunk servers, in minutes. Default value is 2.
    Splunk Failure Count AlertNumber of consecutive Splunk connectivity failures that will trigger an initial HipChat notification (if the HipChat add-on is configured). Default value is 5.
    Splunk Failure Count IntervalNumber of consecutive Splunk connectivity failures that will trigger a subsequent HipChat notification, after the initial failure notification. The add-on will continue to send these updates until the Splunk server is back online. Default value is 10.
    Splunk Resend IntervalHow often the add-on tries to resend any issues that haven’t been successfully sent to Splunk, in minutes. Default value is 3.
    Use Strict ModeWhether SSL certificates are verified. Default value is true. If you are using a self-signed certificate on your Splunk servers, set this value to false to disable SSL verification. To turn Strict Mode back on, you must set the value to true, and then restart your JSD instance.


  5. Click Save Settings.

Next Steps

If necessary, add, modify, or delete Splunk server connections in JSD.