Service Availability Monitoring

Warning: Splunk AppDynamics is ended support for Service Availability Monitoring. Customers who have never purchased SAM will no longer be able to do so. Renewals and additional licenses by existing customers of SAM that are purchased before June 2021, for a one-year term only, are permitted. All existing users of SAM can continue to use it. See Support Advisory: Service Availability Monitoring End of Life (EOL) Notice.

To access Service Availability Monitoring, select Home > Servers > Service Availability (left navigation menu).

The Service Availability Monitoring feature of Server Visibility enables you to monitor internal or external HTTP and HTTPS services. You configure service monitoring from the Controller UI. After you configure monitoring for a service, Service Availability Monitoring evaluates the service:

  • The Agent evaluates each response, based on your specified violation rules, and flags each response as failed (rule violation) or successful (no violation).
  • The service monitor maintains a rolling buffer of evaluated responses. This buffer has a configurable window size (number of evaluated responses), success threshold (number of successful responses), and failure ratio (number of failed responses).
  • The monitor collects evaluated responses until the response buffer is full. Then, it evaluates the service as:
    • NORMAL - Successful responses are greater than or equal to the success threshold.
    • CRITICAL - Failed responses are greater than or equal to the failure threshold.
  • When the buffer is full, the monitor re-evaluates the service every time it evaluates a new response.

For example, with the following values:

  • Success threshold = 3
  • Failure threshold = 1
  • Results window size = 5

The Agent waits until five check results are received, and from these five results, if there is one failure, then the target state is CRITICAL. If there are at least three successful results, then the target state is NORMAL.