Configure the SolarWinds monitor connector instance to receive events from the SolarWinds monitor.

Before you begin

Supported versions:
  • SAM 6.2.1
  • NPM 2024.1
Note: The SolarWinds monitor connector instance can import events from:
  • Network Performance Monitor (NPM)
  • SolarWinds Service & Application Monitor (SAM)

The SolarWinds monitor connector instance requires a credential that lets the instance access SolarWinds monitor accounts. You can use an existing credential or create a new one. The provided user must have access to the SolarWinds API to receive events from the SolarWinds connector.

Role required: evt_mgmt_admin and evt_mgmt_integration

About this task

This connector has the debug and logPayloadForDebug log parameters enabled. The debug parameter logs debug messages, such as calls made to the source system to retrieve events. The logPayloadForDebug parameter logs event and metric payloads from the source system. Once debugging is complete, set this parameter to false to prevent overloading the system.

Procedure

  1. Navigate to All > Event Management > Integrations > Connector Instances.
  2. Click New.
  3. On the form, fill in the fields.
  4. Right-click the form header and select Save.
    The connector instance values are added to the form and the parameters that are relevant to the connector appear.
  5. In the Connector Instance Values section, specify these fields:
    Field Value
    initial_sync_in_days Specify how many days the initial pull must contain to retrieve events. The default value is 7 days.
    nodes_custom_properties Specify the SolarWind monitor property names that are associated with the relevant node. This information is added to the Additional Information field of the event in JSON format. The SolarWinds monitor custom properties are user-defined fields, for example, country, building, or serial number, that you can associate with monitored network objects. Separate multiple entries with a comma.
    Port Specify the value of the port. By default, the value is 17774.
    Note: For version 2023.1 and above, the port is 17774.
  6. (Optional) Name of a MID Server.
    If no MID Server is specified, an available MID Server that has a matching IP range is used. In the MID Servers for Connectors section, specify a MID Server that is up and valid. You can configure several MID Servers. If the first is down, the next MID Server is used. If that MID Server is not available, the next is selected, and so on. MID Servers are sorted according to the order that their details were entered into the MID Server for Connectors section. The privileges that are required for the user account that is used for the MID Server to collect events from SolarWinds monitor is that of evt_mgmt_integration.
  7. Click Test connector to verify the connection between the MID Server and the SolarWinds monitor connector.
    If the test fails, follow the instructions that are issued by the error to correct the problem and then run another test.
    Note: Use a network tool, such as ping, to verify credential correctness and network connectivity from the MID Server to SolarWinds monitor.
  8. After a successful test, select the Active check box and then click Update.