Identify and resolve website issues faster by piping notification from Freshping into Freshservice Alert Management. Benefit from reduced noise and automated creation and routing of rich incidents. 

Configuration in Freshservice:

Step 1:

Head to the Admin panel, scroll down to IT Operations Management, and select Monitoring Tools

If your account has more than one workspace, navigate to Admin > {Worskpace Name} > IT Operations Management> Monitoring Tools.

Step 2:

You are now on the Monitoring Tools list page. Select Add monitoring tool to add a new integration.

Step 3

You will see a list of pre-configured integrations, the gateway to custom integration using webhooks, and the option to use email as a channel for alerts. Select Freshping

Step 4

Get the Endpoint URL and the Auth key for Freshping by following the integration setup.

Configuration in Freshping

  1. Go to Freshping and Navigate to Settings -> Integration.
  2. Under Webhook click on Create Integration and paste the copied endpoint URL and click on Create

Once you've configured the integration, it’ll be listed in the integrations page Choose to enable/ disable the integration at any point

Click on +Add integration on the right to create new integrations for your monitoring tools

Where can I find my Freshping account domain and API Key?

  1. Login to your Freshping account

  2. Navigate to Settings > Account Settings in your Freshping account, where you can find your Freshping account domain name or in short Freshping URL

  3. You can find the API Key right below in the second section

Once Freshping is selected and the Alert Profile is created, follow the steps listed below:

Step 1: Configure Incoming Alerts

  1. Add the Name and Description of your integration. For default integrations, we display a sample content of the alert sent from the monitoring tool. You can choose to edit it if you have configured a custom content in your alert notifications. 

  2. Configure Alert Content - Freshping Payload

  3. Once you're done click on Save & Next 

Freshping Webhook test data 


    "request_start_time": "2021-01-20T14:54:04.197877+00:00",

    "check_target_response_time": 100,

    "check_id": 1,

    "recently_started_check_start_time": null,

    "recently_started_check_http_status_code": null,

    "http_status_code": 200,

    "check_state_name": "Available",

    "check_name": "Example check",

    "recently_started_check_state_name": null,

    "application_name": "Webhook test",

    "recently_started_check_response_time": null,

    "request_url": "",

    "check_computed_target_response_time": 200,

    "response_time": 50


Freshping Production Live Data


   "request_start_time": "2021-01-21T11:28:01.651346+00:00",

   "application_id": 9004,

   "check_id": 30979,

   "recently_started_check_start_time": null,

   "recently_started_check_http_status_code": null,

   "http_status_code": 200,

   "check_state_name": "Degraded Performance",

   "check_name": "ABC Track Admin UI",

   "recently_started_check_state_name": null,

   "recently_started_check_response_time": null,

   "application_name": "Default Group",

   "check_target_response_time": 1000.0,

   "request_url": "",

   "check_computed_target_response_time": 1000.0,

   "response_time": 9253


Step 2: Map Alert fields

You can configure the alert information that you want to see in Freshservice to be able to effectively resolve any issue. Alert notifications generated repeatedly for the same issue are grouped based on Resource and Metric values and created as a single alert record in Freshservice.

  1. Hover over the alert fields and click on the "+" icon to map the alert fields in your monitoring tool to the corresponding Freshservice fields

Freshservice Alert Fields


Freshping Payload


Denotes the name of the monitored entity. It could be the hostname, application name or service name based on the type of the resource. Ex : BLR_PEPLINK, IBM_asset, RDS, ELB,etc

This field is mandatory.


ABC Track Admin UI (Live Data)

Metric Name

The performance aspect of the resource that is monitored. Ex: CPU Utilisation, Throughput, etc

This field is mandatory


ABC Track Admin UI (Live Data)

Metric Value

Value of the monitored metric. Ex: 50% CPU Utilised


9253 (Live Data)


Denotes the MAC address or IP address of the machine 



Message denotes the context of the alert. 


Description of the issue



200 (Live Data )

1000 (Live Data)


Severity denotes the impact of the alert and the urgency with which it has been acted upon


Degraded Performance (Live Data)


Tags help you classify the incoming alerts using keywords


Additional Information

Select up to 5 fields to additional information about your alert

Request_url,check_id,http_status_code,application_name (Live Data)

30979 (Live Data)

Default Group (Live Data)

Occurrence Time

Time of creation of an alert


2021-01-21T11:28:01.651346+00:00 (Live Data)

Click on Save & Next to proceed to the next step

Step 3: Map Alert Severity

Severities help you understand how quickly an issue has to be acted upon. You can filter alerts based on the alert severity mapping 

  1. Map the severity of an alert from your monitoring tool (Freshping) to a corresponding severity in Freshservice and click Save and Next

Severity ( Freshservice) 

Severity ( Freshping )


Not Responding,

String Check Matching failure,                                              

Status Code check failure


Reporting Error


Performance Degraded



Good Performance

Step 4: Authorise Integration

  1. Copy the Endpoint URL to be configured in your Freshping Monitoring tool 

  2. Click on Enable

  3. Go to Freshping and Navigate to Settings -> Integration.

  4. Under Webhook click on The Create Integration and Paste the Copied Endpoint URL and click on Create


Once you've configured the integration, it’ll be listed in the integrations page 

  1. Choose to enable/ disable the integration at any point

  2. Click on +Add integration on the right to create new integrations for your monitoring tools