@@ -70,6 +70,7 @@ If you are already familiar with SkyWalking, you could use this catalog to find
...
@@ -70,6 +70,7 @@ If you are already familiar with SkyWalking, you could use this catalog to find
* Use [ALS (access log service)](https://www.envoyproxy.io/docs/envoy/latest/api-v2/service/accesslog/v2/als.proto) to observe service mesh, without Mixer. Follow [document](en/setup/envoy/als_setting.md) to open it.
* Use [ALS (access log service)](https://www.envoyproxy.io/docs/envoy/latest/api-v2/service/accesslog/v2/als.proto) to observe service mesh, without Mixer. Follow [document](en/setup/envoy/als_setting.md) to open it.
*[Backend, UI and CLI setup document](en/setup/backend/backend-ui-setup.md).
*[Backend, UI and CLI setup document](en/setup/backend/backend-ui-setup.md).
*[Configuration Vocabulary](en/setup/backend/configuration-vocabulary.md). Configuration Vocabulary lists all available configurations provided by `application.yml`.
*[Overriding settings](en/setup/backend/backend-setting-override.md) in application.yml is supported.
*[Overriding settings](en/setup/backend/backend-setting-override.md) in application.yml is supported.
*[IP and port setting](en/setup/backend/backend-ip-port.md). Introduces how IP and port set can be used.
*[IP and port setting](en/setup/backend/backend-ip-port.md). Introduces how IP and port set can be used.
*[Backend init mode startup](en/setup/backend/backend-init-mode.md). How to init the environment and exit graciously. Read this before you try to start a new cluster.
*[Backend init mode startup](en/setup/backend/backend-init-mode.md). How to init the environment and exit graciously. Read this before you try to start a new cluster.
dayStep:${SW_STORAGE_DAY_STEP:1}# Represent the number of days in the one minute/hour/day index.
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.
dayStep:${SW_STORAGE_DAY_STEP:1}# Represent the number of days in the one minute/hour/day index.
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.
# Batch process setting, refer to https://www.elastic.co/guide/en/elasticsearch/client/java-api/5.5/java-docs-bulk-processor.html
bulkActions:${SW_STORAGE_ES_BULK_ACTIONS:2000}# Execute the bulk every 2000 requests
bulkSize:${SW_STORAGE_ES_BULK_SIZE:20}# flush the bulk every 20mb
flushInterval:${SW_STORAGE_ES_FLUSH_INTERVAL:10}# flush the bulk every 10 seconds whatever the number of requests
concurrentRequests:${SW_STORAGE_ES_CONCURRENT_REQUESTS:2}# the number of concurrent requests
advanced:${SW_STORAGE_ES_ADVANCED:""}
```
```
- File at `trustStorePath` is being monitored, once it is changed, the ElasticSearch client will do reconnecting.
- File at `trustStorePath` is being monitored, once it is changed, the ElasticSearch client will do reconnecting.
-`trustStorePass` could be changed on the runtime through [**Secrets Management File Of ElasticSearch Authentication**](#secrets-management-file-of-elasticsearch-authentication).
-`trustStorePass` could be changed on the runtime through [**Secrets Management File Of ElasticSearch Authentication**](#secrets-management-file-of-elasticsearch-authentication).
topNReportPeriod:${SW_CORE_TOPN_REPORT_PERIOD:10}# top_n record worker report cycle, unit is minute
topNReportPeriod:${SW_CORE_TOPN_REPORT_PERIOD:10}# top_n record worker report cycle, unit is minute
...
@@ -97,10 +96,9 @@ storage:
...
@@ -97,10 +96,9 @@ storage:
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.
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.
indexShardsNumber:${SW_STORAGE_ES_INDEX_SHARDS_NUMBER:1}# The index shards number is for store metrics data rather than basic segment record
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.
# Batch process setting, refer to https://www.elastic.co/guide/en/elasticsearch/client/java-api/5.5/java-docs-bulk-processor.html
bulkActions:${SW_STORAGE_ES_BULK_ACTIONS:1000}# Execute the bulk every 1000 requests
bulkActions:${SW_STORAGE_ES_BULK_ACTIONS:1000}# Execute the bulk every 1000 requests
flushInterval:${SW_STORAGE_ES_FLUSH_INTERVAL:10}# flush the bulk every 10 seconds whatever the number of requests
flushInterval:${SW_STORAGE_ES_FLUSH_INTERVAL:10}# flush the bulk every 10 seconds whatever the number of requests
concurrentRequests:${SW_STORAGE_ES_CONCURRENT_REQUESTS:2}# the number of concurrent requests
concurrentRequests:${SW_STORAGE_ES_CONCURRENT_REQUESTS:2}# the number of concurrent requests
...
@@ -119,10 +117,9 @@ storage:
...
@@ -119,10 +117,9 @@ storage:
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.
indexShardsNumber:${SW_STORAGE_ES_INDEX_SHARDS_NUMBER:1}# The index shards number is for store metrics data rather than basic segment record
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.