APMのMetricSetsについて 🔗
MetricSets are key performance indicators, like request rate, error rate, and request duration, that are calculated from traces and spans in Splunk APM. There are 2 categories of MetricSets: Troubleshooting MetricSets (TMS), used for high-cardinality troubleshooting, and Monitoring MetricSets (MMS), used for real-time monitoring. MetricSets are similar to the metric time series (MTS) used in Splunk Infrastructure Monitoring to populate charts and generate alerts. See メトリック時系列 to learn more. MetricSets are MTS that are specific to Splunk APM.
Troubleshooting MetricSets 🔗
Troubleshooting MetricSets (TMS) are metric time series (MTS) you can use for troubleshooting high-cardinality identities in APM. You can also use TMS to make historical comparisons across spans and workflows.
Splunk APMは、デフォルトでいくつかのスパンタグをインデックス化しTroubleshooting MetricSetsを生成します。これらの各タグの詳細については、APMのデフォルトのインデックス付きスパンタグ を参照してください。APMによるこれらのスパンタグのインデックス化を変更したり停止したりすることはできません。
You can also create custom TMS by indexing additional span tags and processes. To learn how to index span tags and processes to generate new Troubleshooting MetricSets, see スパンタグをインデックス化してTroubleshooting MetricSetsを生成する.
利用可能なTMSメトリクス 🔗
Every TMS generates the following metrics, known as request, error, and duration (RED) metrics. RED metrics appear when you select a service in the service map. See シナリオ：KaiがSplunk APMのサービスマップを使用してエラーの根本原因を調査する to learn more about using RED metrics in the service map.
リクエスト率
エラー率
根本原因エラー率
P50、P90、P99レイテンシ
Troubleshooting MetricSetsの測定精度は10秒です。Splunk APMは、各10秒のレポートウィンドウについて、メトリクスの分散から分位数をレポートします。
Use TMS within Splunk APM 🔗
TMS appear on the service map and in Tag Spotlight. Use TMS to filter the service map and create breakdowns across the values of a given indexed span tag or process.
See サービスマップでサービス間の依存関係を表示する and Tag Spotlightを使用してサービスパフォーマンスを分析する.
TMS retention period 🔗
Splunk Observability Cloud retains TMS for the same amount of time as raw traces. By default, the retention period is 8 days.
Troubleshooting MetricSetsの詳細については、スパンタグとTroubleshooting MetricSetsのリファレンスおよびベストプラクティス を参照してください。
Monitoring MetricSetsメトリックセットの監視 🔗
Monitoring MetricSets (MMS) are metric time series (MTS) that power the real-time monitoring capabilities in Splunk APM, including charts and dashboards. MMS power the APM landing page and the dashboard view. MMS are also the metrics that detectors monitor to generate alerts.
MMSは、特定のエンドポイント、またはサービス内のすべてのエンドポイントの集合体に対して利用可能です。
Endpoint-level MMS reflect the activity of a single endpoint in a service, while service-level MMS aggregate the activity of all of the endpoints in the service. MMS are limited to spans where the span.kind has a value of SERVER or CONSUMER.
次のような場合、スパンは、kind の値がなかったり、kind の値が異なったりする可能性があります：
スパンの起点が、自己開始型の操作または推定サービスである場合
インストルメンテーションでエラーが発生した場合
In addition to the following default MMS, you can create custom MMS. See カスタムディメンションを使用してMonitoring MetricSetsを生成する.
Available default MMS metrics and dimensions 🔗
MMS are available for the following APM components:
service.request
spans
traces
workflows (Workflow metrics are created by default when you create a Business Workflow. Custom MMS are not available for Business Workflows.)
Each MMS includes 6 metrics for each component. For histogram MMS, there is a single metric for each component. Use the histogram functions to access the specific histogram bucket you want to use.
For each metric, there is 1 metric time series (MTS) with responses sf_error: true or sf_error: false.
説明 |
MMS |
Histogram MMS |
|---|---|---|
Request count |
|
|
Minimum request duration |
|
|
Maximum request duration |
|
|
Median request duration |
|
|
Percentile request duration |
|
|
Percentile request duration |
|
|
Each MMS has a set of dimensions you can use to monitor and alert on service performance.
Service dimensions 🔗
sf_environmentdeployment.environment- This dimension is only available for histogram MMS.sf_serviceservice.name- This dimension is only available for histogram MMS.sf_error
Span dimensions 🔗
sf_environmentdeployment.environment- This dimension is only available for histogram MMS.sf_serviceservice.name- This dimension is only available for histogram MMS.sf_operationsf_kindsf_errorsf_httpMethod（該当する場合）
Trace dimensions 🔗
sf_environmentdeployment.environment- This dimension is only available for histogram MMS.sf_serviceservice.name- This dimension is only available for histogram MMS.sf_operationsf_httpMethodsf_error
Workflow dimensions 🔗
Workflow metrics and dimensions are created by default when you create a Business Workflow.
sf_environmentdeployment.environment- This dimension is only available for histogram MMS.sf_workflowsf_error
Use MMS within Splunk APM 🔗
Use MMS for alerting and real-time monitoring in Splunk APM. You can create charts, dashboards, and alerts based on Monitoring MetricSets.
タスク |
ドキュメント |
|---|---|
チャートの作成 |
|
ダッシュボードの作成 |
|
アラートの作成 |
|
APMダッシュボードでのサービスの監視 |
MMS retention period 🔗
Splunk Observability Cloud stores MMS for 13 months by default.
Monitoring MetricSetsとTroubleshooting MetricSetsの比較 🔗
Because endpoint-level and service-level MMS include a subset of the TMS metrics, you might notice that metric values for a service are different depending on the context in Splunk APM. This is because MMS are the basis of the dashboard view and MMS can only have a kind of SERVER or CONSUMER. In contrast, TMS are the basis of the troubleshooting and Tag Spotlight views and TMS aren’t restricted to specific metrics.
For example, values for checkout service metrics displayed in the host dashboard might be different from the metrics displayed in the service map because there are multiple span kind values associated with this service that the MMS that power the dashboard don’t monitor.
To compare MMS and TMS directly, restrict your TMS to endpoint-only data by filtering to a specific endpoint. You can also break down the service map by endpoint.