From 29104848a6d65008fb7e00c5b4f50c41e67945a0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E5=90=B4=E6=99=9F=20Wu=20Sheng?= Date: Wed, 22 Sep 2021 09:13:10 +0800 Subject: [PATCH] Update ttl.md to add another 2 types of model relating to recordTTL (#7760) --- docs/en/setup/backend/ttl.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/en/setup/backend/ttl.md b/docs/en/setup/backend/ttl.md index 779e4e89b7..1fc599f4b0 100644 --- a/docs/en/setup/backend/ttl.md +++ b/docs/en/setup/backend/ttl.md @@ -1,7 +1,7 @@ # TTL -In SkyWalking, besides metadata, there are two types of observability data: -1. Record: Includes trace and alarm. Log may also be included in the future. -1. Metric: Includes percentile, heat map, success rate, cpm (rpm), etc. +In SkyWalking, there are two types of observability data: +1. Records include traces, logs, topN sampled statements and alarm. `recordDataTTL` applies to **record** data. +1. Metrics include all metrics for service, instance, endpoint, and topology map. Metadata(lists of services, instances, or endpoints) also belongs to metrics. `metricsDataTTL` applies to **Metrics** data. These are the settings for the different types: ```yaml @@ -10,5 +10,3 @@ These are the settings for the different types: metricsDataTTL: ${SW_CORE_METRICS_DATA_TTL:7} # Unit is day ``` -- `recordDataTTL` applies to **record** data, including tracing and alarm. -- `metricsDataTTL` applies to all metrics, including the metrics for service, instance, endpoint, and topology map.