---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure PRTG connector

# Configure PRTG connector {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Configure the PRTG connector instance to receive alerts from a Paessler PRTG Network
Monitor source.

## Before you begin

Role required: evt_mgmt_admin

Supported version: 21.3.71.

## Procedure

1. Navigate to AllEvent ManagementIntegrationsConnector Instances.
2. Click New and create a connector instance with the following details:  
   {#configure-prtg-connector__table_bqf_1m2_sbb__entry__2}

   | Field | Value |
   |-|-|
   | Name | Descriptive name for the PRTG connector. |
   | Description | Description for the use of the PRTG event collection instance. |
   | Host IP | Specify the PRTG IP address. |
   | Credential | Either select the required credentials from the list or click New and create the required credentials. If you create the credentials, save them using a unique and recognizable name, for example, <kbd class="ph userinput">PRTGOPS</kbd>. |
   | Event collection last run time | The last run time value is automatically updated. |
   | Last event collection status | The last run time status is automatically updated. |
   | Event collection schedule (seconds) | The frequency in seconds that the system checks for new events from PRTG. |
   | Last error message | The last error message is automatically updated. |
   | Connector definition | Select PRTG. |
   | Connector Instance Values section | The parameters that are specific to PRTG display here when the form is saved. |
   | MID Servers (MID Server for Connectors section) | 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. |
   [ ]

   {#configure-prtg-connector__table_bqf_1m2_sbb}
3. 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.
4. In the Connector Instance Values section, specify the PRTG values.
   1. add_columns.  
      Specify which columns to be returned by the connector. Separate the names with a comma and without a space between the names. The output is stored in the Additional information field of the event. Default value <kbd class="ph userinput">false</kbd>. If <kbd class="ph userinput">false</kbd> is specified, only the default list of columns is retrieved: parent, name, type, objid, tags, message, status, priority, datetime, actions, baselink, basetype, modifiedby.  
      Note:  
      Only columns names that are applicable to the Message content type can be specified.
   2. date_format.  
      The format date and time. Default format M/d/yyyy/ h:mm:ss a. If you receive an event whose date is in a different format, modify this value to match the format of the incoming event. If you do not, the event will not be processed correctly.

      For example, if an event arrives on June 27, 2019 at 11:25 AM
      with a listed date of 2019/06/27/ 11:25:00 a, modify
      the date_format value to yyyy/M/d/ h:mm:ss a to match the format of the received event.

      In the date_format, <kbd class="ph userinput">a</kbd>
      represents AM, and <kbd class="ph userinput">p</kbd> represents PM.
   3. In the days_from field, specify the number of days for which events must be collected at the first collection cycle.  
      Default value <kbd class="ph userinput">7</kbd> days.
   4. debug.  
      Default value <kbd class="ph userinput">false</kbd>.
   5. port.  
      Default value <kbd class="ph userinput">80</kbd>.
   6. protocol.  
      The default protocol type is <kbd class="ph userinput">http</kbd>.
   7. prtg_api_fetched_events_num.  
      Maximum number of events, per query, that can be fetched from the PRTG client into the MID Server. Default number: <kbd class="ph userinput">50,000</kbd>.
   8. time_zone.  
      The default time zone is the <kbd class="ph userinput">GMT</kbd> time zone; update this value to the PRTG time zone. For example, if PRTG is sending events according to the <kbd class="ph userinput">EDT</kbd> time zone, update this value to <kbd class="ph userinput">GMT-4</kbd> (abbreviations such as EDT are not supported).
   {#configure-prtg-connector__substeps_qlz_mz1_55}
5. Right-click the form header and select Save.
6. Click Test Connector to verify the connection between the MID Server and the connector.
7. If the test fails, follow the instructions that the error issues to correct the problem and then run another test.  
   If this message appears: Connection test failed: Failed to connect to PRTG on test connector. Invalid API Key, then enter the API Key for the specific user to be able to read the PRTG events.  
   Note:  
   Use a network tool, such as ping, to verify credential correctness and network connectivity from the MID Server to PRTG.
8. After a successful test, select the Active check box and then click Update.
{#configure-prtg-connector__steps_sz4_wz1_kz}

*[\>]: and then