Prerequisites

  • OpsRamp Classic gateway version 14.0.0 and above.

  • OpsRamp Nextgen gateway version 14.0.0 and above.

    Note: We recommend using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc.

Configure HTTP Endpoint Probe Integration

Click here to Configure and Install the HTTP Endpoint Probe Integration
  1. To select your client, navigate to All Clients, and click the Client/Partner dropdown menu.
    Note: You may either type your client’s name in the search bar or select your client from the list.
  2. Navigate to Setup > Account. The Account Details screen is displayed.
  3. Click Integrations. The Installed Integrations screen is displayed with all the installed applications.
    Note: If you do not have any installed applications, you will be navigated to the Available Integrations and Apps page with all the available applications along with the newly created application with the version.
  4. Click + ADD on the Installed Integrations page.
    Note: Search for the integration either by entering the name of the integration in the search bar or by selecting the category of the integration from the All Categories dropdown list.
  5. Click ADD in the HTTP Endpoint Probe application.
  6. In the Configuration screen, click + ADD. The Add Configuration screen appears.
  7. Enter the following BASIC INFORMATION:


Field NameDescriptionField Type
NameEnter the name for the configuration.String
Base URLEndpoint URL to be monitored.String
Timeout(ms)Time interval to wait for a response from the configured URL, in milliseconds.

Note: By default 60000 is the timeout.
String
Additional configurationA JSON data structure with additional configuration parameters:
  • Uripath = (optional) Additional path elements appended to the base URL.
  • ResContentShouldContain = (optional) String/pattern to match on in the response from the configured URL.
  • ResContentShouldNotContain = (optional) String/pattern that should not be present in the response from configured URL.
  • Method = GET HTTP method or POST HTTP method.
  • HttpHeaders = (optional) Additional headers that might be required for the URL.
  • HttpParams = (optional) Applicable for all request types.
  • PostData = (optional) Applicable for HTTP method types POST or PATCH.
Integer
App Failure NotificationIf turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.Checkbox
Additional Configuration:
{
"Method":"POST",
"ResContentShouldContain":"",
"ResContentShouldNotContain":"",
"HttpHeaders":{"content-type":"application/json"},
"HttpParams":{},
"PostData":"{ \"name\": \"morpheus\", \"job\": \"zion resident\"}",
"UrlPath":"api/users"}
  1. CUSTOM ATTRIBUTES: Custom attributes are the user-defined data fields or properties that can be added to the preexisting attributes to configure the integration.
Field NameDescriptionField Type
Custom AttributeSelect the custom attribute from the dropdown. You can add attributes by clicking the Add icon (+).Dropdown
ValueSelect the value from the dropdown.Dropdown

Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).

  1. In the RESOURCE TYPE section, select:
    • ALL: All the existing and future resources will be discovered.
    • SELECT: You can select one or multiple resources to be discovered.
  2. In the DISCOVERY SCHEDULE section, select recurrence pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
  3. Click ADD.


Now the configuration is saved and displayed on the configurations page after you save it.
Note: From the same page, you may Edit and Remove the created configuration.
12. Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.
Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.
13. Click NEXT.
14. (Optional) Click +ADD to create a new collector. You can either use the pre-populated name or give the name to your collector.
15. Select an existing registered profile.


  1. Click FINISH.
    The integration is installed and displayed on the INSTALLED INTEGRATION page. Use the search field to find the installed integration.

Modify HTTP Endpoint Probe Integration

Click here to Modify the Configuration

Discover Resources in HTTP Endpoint Probe Integration

Click here to View the HTTP Endpoint Probe Details

To discover resources for HTTP Endpoint Probe:

  1. Navigate to Infrastructure > Search > NETWORK SERVCIES > HTTP Endpoint Probe. The HTTP Endpoint Probe page is displayed
  2. Select the application on the HTTP Endpoint Probe page
  3. The RESOURCE page appears from the right.
  4. Click the ellipsis () on the top right and select View Details.


  1. Navigate to the Attributes tab to view the discovery details.


View resource metrics

To confirm HTTP Endpoint Probe monitoring, review the following:

  • Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
  • Alerts: Alerts are generated for metrics that are configured as defined for integration.
  1. Click the Metrics tab to view the metric details for HTTP Endpoint Probe.