サービスアベイラビリティのモニタリング

警告: Splunk AppDynamics は、サービス可用性のモニタリングのサポートを終了しました。SAM を購入していないお客様は購入できなくなります。2021 年 6 月より前に購入した SAM の既存のお客様による更新および追加ライセンスは利用可能です（1 年の期間のみ）。SAM の既存のすべてのユーザは引き続き使用できます。「サポートアドバイザリ：サービス可用性モニタリングのサポート終了（EOL）通知」を参照してください。

サービス可用性のモニタリングにアクセスするには、[Home ] > [Servers] > [Service Availability]（左ナビゲーションメニュー）の順に選択します。

サーバの可視性のサービス可用性のモニタリング機能を使用すると、内部または外部の HTTP および HTTPS サービスをモニタできます。コントローラ UI からサービスモニタリングを設定します。サービスのモニタリングを設定した後、サービス可用性のモニタリングによりサービスが評価されます。

  • エージェントは、指定された違反ルールに基づいて各応答を評価し、各応答に failed（ルール違反）または successful（違反なし）のフラグを付けます。
  • サービスモニタは、評価された応答のローリングバッファを維持します。このバッファには、設定可能なウィンドウサイズ（評価された応答の数）、成功しきい値（成功した応答の数）、および失敗率（失敗した応答の数）があります。
  • モニタは、応答バッファがいっぱいになるまで、評価された応答を収集します。次に、サービスを次のように評価します。
    • NORMAL：成功応答が成功しきい値以上。
    • CRITICAL：失敗応答が失敗しきい値以上。
  • バッファがいっぱいになると、モニタは新しい応答を評価するたびにサービスを再評価します。

たとえば、次の値を指定します。

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

エージェントは、チェック結果が 5 つ受信されるまで待機します。それらの 5 つの結果のうち失敗が 1 つある場合、ターゲットの状態は CRITICAL になります。成功結果が 3 つ以上ある場合、ターゲットの状態は NORMAL になります。

Viewing the Monitored Services

You can view the monitored services in the Monitored Services list. The state is determined by evaluating the Response Validators during the results window. Response Validators are rules you configure that are used to evaluate against the responses received from the service.

The possible states are:

  • NORMAL - The number of successful responses in the result window is greater than or equal to the configured success threshold.
  • CRITICAL - The number of failed responses in the result window is greater than or equal to the configured failed threshold.
  • UNKNOWN - If the Machine Agent does not provide any data.

Monitored Services List

From the top navigation bar, select Servers > Service Availability to view a list of monitored services. Use the action toolbar to manage your monitored services by adding new ones, viewing details, and so on.

Service Availability

Monitored Service Details

Select a monitored service, and double-click to view the associated details.

Monitored Service Details

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.

注意: 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.
    注: 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

Monitoring the Service Health

An event is sent to the Controller for every state change and periodically (by default every 5 minutes).
  1. You can change the update interval by setting the System property: appdynamics.machine.agent.sam.event.updateIntervalMillis. See Configuration Property Reference.
  2. The events are visible from the Monitored Service details panel and from the Server Visibility Events list.Server Visibility Events List
  3. Double-click the event to review details. Event Details
  4. The event properties are as follows:
    オプション説明
    CategoryCUSTOM
    Event TypeService Availability
    Propertyseverity
    注: Values can be ERROR (failure) or INFO (passing).

Configuring Alerts

To create alerts for your monitored services:

  1. From the Servers panel, select Alert & Respond.
  2. Select Policies.
  3. Select Create Policy Manually. If policies already exist, you may not see this option. Click + to add a policy manually.
  4. Under Custom Events, click + to Add Custom Event.Add Custom Event Filter
  5. In the Actions section of the Policy panel, add the action you want to execute if the policy violates and save the policy.