dayStep:${SW_STORAGE_DAY_STEP:1}# Represent the number of days in the one minute/hour/day index.
dayStep:${SW_STORAGE_DAY_STEP:1}# Represent the number of days in the one minute/hour/day index.
superDatasetDayStep:${SW_SUPERDATASET_STORAGE_DAY_STEP:-1}# Represent the number of days in the super size dataset record index, the default value is the same as dayStep when the value lt 0
user:${SW_ES_USER:""}
user:${SW_ES_USER:""}
password:${SW_ES_PASSWORD:""}
password:${SW_ES_PASSWORD:""}
secretsManagementFile:${SW_ES_SECRETS_MANAGEMENT_FILE:""}# Secrets management file in the properties format includes the username, password, which are managed by 3rd party tool.
secretsManagementFile:${SW_ES_SECRETS_MANAGEMENT_FILE:""}# Secrets management file in the properties format includes the username, password, which are managed by 3rd party tool.
...
@@ -105,6 +106,9 @@ Such as, if dayStep == 11,
...
@@ -105,6 +106,9 @@ Such as, if dayStep == 11,
1. data in [2000-01-01, 2000-01-11] will be merged into the index-20000101.
1. data in [2000-01-01, 2000-01-11] will be merged into the index-20000101.
1. data in [2000-01-12, 2000-01-22] will be merged into the index-20000112.
1. data in [2000-01-12, 2000-01-22] will be merged into the index-20000112.
`storage/elasticsearch/superDatasetDayStep` override the `storage/elasticsearch/dayStep` if the value is positive.
This would affect the record related entities, such as the trace segment. In some cases, the size of metrics is much less than the record(trace), this would help the shards balance in the ElasticSearch cluster.
NOTICE, TTL deletion would be affected by these. You should set an extra more dayStep in your TTL. Such as you want to TTL == 30 days and dayStep == 10, you actually need to set TTL = 40;
NOTICE, TTL deletion would be affected by these. You should set an extra more dayStep in your TTL. Such as you want to TTL == 30 days and dayStep == 10, you actually need to set TTL = 40;
### Secrets Management File Of ElasticSearch Authentication
### Secrets Management File Of ElasticSearch Authentication
secretsManagementFile:${SW_ES_SECRETS_MANAGEMENT_FILE:""}# Secrets management file in the properties format includes the username, password, which are managed by 3rd party tool.
secretsManagementFile:${SW_ES_SECRETS_MANAGEMENT_FILE:""}# Secrets management file in the properties format includes the username, password, which are managed by 3rd party tool.
dayStep:${SW_STORAGE_DAY_STEP:1}# Represent the number of days in the one minute/hour/day index.
dayStep:${SW_STORAGE_DAY_STEP:1}# Represent the number of days in the one minute/hour/day index.
superDatasetDayStep:${SW_SUPERDATASET_STORAGE_DAY_STEP:-1}# Represent the number of days in the super size dataset record index, the default value is the same as dayStep when the value is less than 0
indexShardsNumber:${SW_STORAGE_ES_INDEX_SHARDS_NUMBER:1}# Shard number of new indexes
indexShardsNumber:${SW_STORAGE_ES_INDEX_SHARDS_NUMBER:1}# Shard number of new indexes
superDatasetIndexShardsFactor:${SW_STORAGE_ES_SUPER_DATASET_INDEX_SHARDS_FACTOR:5}# Super data set has been defined in the codes, such as trace segments. This factor provides more shards for the super data set, shards number = indexShardsNumber * superDatasetIndexShardsFactor. Also, this factor effects Zipkin and Jaeger traces.
superDatasetIndexShardsFactor:${SW_STORAGE_ES_SUPER_DATASET_INDEX_SHARDS_FACTOR:5}# Super data set has been defined in the codes, such as trace segments. This factor provides more shards for the super data set, shards number = indexShardsNumber * superDatasetIndexShardsFactor. Also, this factor effects Zipkin and Jaeger traces.
dayStep:${SW_STORAGE_DAY_STEP:1}# Represent the number of days in the one minute/hour/day index.
dayStep:${SW_STORAGE_DAY_STEP:1}# Represent the number of days in the one minute/hour/day index.
superDatasetDayStep:${SW_SUPERDATASET_STORAGE_DAY_STEP:-1}# Represent the number of days in the super size dataset record index, the default value is the same as dayStep when the value is less than 0
user:${SW_ES_USER:""}
user:${SW_ES_USER:""}
password:${SW_ES_PASSWORD:""}
password:${SW_ES_PASSWORD:""}
secretsManagementFile:${SW_ES_SECRETS_MANAGEMENT_FILE:""}# Secrets management file in the properties format includes the username, password, which are managed by 3rd party tool.
secretsManagementFile:${SW_ES_SECRETS_MANAGEMENT_FILE:""}# Secrets management file in the properties format includes the username, password, which are managed by 3rd party tool.