Since v9.2.0, SkyWalking OAP provides 2 storage options for all data, including metadata, metrics, traces, logs, events, profiling data, etc.. OAP exposes a system environment variable (SW_STORAGE_ES_LOGIC_SHARDING
) to control the running mode.
SW_STORAGE_ES_LOGIC_SHARDING = false
)This is the new mode introduced in 9.2.0. It prefers to keep data with similar properties in one index template, such as all metrics and metadata.
metrics-all
and records-all
.metric_table
or record_table
.@ElasticSearch.Column()
), the alias would be the real physical column name.The super dataset would not be affected by this, such as traces and logs.
SW_STORAGE_ES_LOGIC_SHARDING = true
)@MetricsFunction
or @MeterFunction
annotation would not be merged. They would be kept in a separate index template.metrics-aggregation function name
or meter-aggregation function name
such as metrics-count
, and the logic index name would be present in column metric_table
.Notice: Users still could choose to adjust ElasticSearch's shard number(SW_STORAGE_ES_INDEX_SHARDS_NUMBER
) to scale out in either mode.