Configure Service Availability

By default, configuration changes take effect within at least two minutes of the change, so you do not need to restart the Machine Agent after changing the configuration. If the protocol, target, or method of a service are changed once a service is created, the state of the service is set to UNKNOWN and is re-evaluated with the new configuration.

CAUTION: To configure this feature, users need the Configure Server Visibility permission.

By default, these addresses are restricted:

  • Loop back address: localhost, 127.0.0.1, ::1(IPv6)
  • Site local address: 192.168.0.0/16, 10.0.0.0/8, 172.16.0.0/12, fec0::/8(IPv6)
  • Link local address: 169.254.0.1 - 169.254.255.254, fe80::/10(IPv6)
  • Any local address: 0.0.0.0, ::(IPV6)
  • Multicast address: 224.0.0.0/4(224.0.0.0 to 239.255.255.255), ff00::/8(IPV6)

To access the configuration panel:

  1. From the Controller top navigation bar, select Servers > Service Availability. A list of monitored services display, if any are configured.
  2. To add a service, select Add. The Add Service Monitoring Configuration panel displays with three tabs.Add Service Monitoring Configuration
  3. From the Main tab, specify the required fields and save the configuration. Each field has an associated tooltip that provides help. See the following table for a description of the Main configuration panel:
    FieldDescriptionDefaultRequired
    NameYour name for this target configuration. This name displays in the Service Availability list.N/AYes
    TargetThe resource to be monitored, for example, http://myThirdPartyService.com/data. Specify which HTTP method to use to send the request (GET, POST, HEAD)N/AYes
    ServerName of the Machine Agent performing the monitoring. Only servers that are enabled for Server Visibility display in the dropdown.N/AYes
    Socket TimeoutHow long to wait, in milliseconds, after a successful connection for a complete HTTP response.30000Yes
    Success thresholdNumber of required successes within the results panel for a NORMAL state.3Yes
    Check IntervalInterval time in between checks in seconds.
    Note: Setting this interval to more than 60 seconds will result in visible gaps in the metric graphs for monitored services.
    		10Yes
    Results Window SizeNumber of most recent results to use in determining the state of the service.5Yes
    Connect TimeoutHow long to wait (in ms) for the service to respond to a connection request.30000Yes
    Failure thresholdNumber of required failures within the result window for a CRITICAL state.1Yes
    Max response sizeMaximum response size to collect in bytes.5000Yes
    Follow redirectsDeprecated. Follow redirect to determine the state of service.NoNo
  4. From the Request Configuration tab, specify your request headers. You can define a list of customized headers to send with requests. For example, the list can mimic desktop or mobile browsers. You can also define a request body for POST requests. You can specify an "Authorization" header", if credentials are required.
    ProtocolFieldValue TypeDefaultDescription
    HTTPheader name and value pairStringemptyCustomized header to send with requests.
    bodyStringemptyAny data to send with the request. Usually used for POST.
  5. From the Response Validators tab, configure your validation rules. You can provide a list of rules for the Machine Agent to use to validate the health of a monitored service. If any rule is violated, the response is considered failed. For each rule you can specify HTTP property, operator, and value. The list of operators varies depending on the property selected in the first dropdown. Edit Configuration