- 10 8月, 2022 2 次提交
-
-
由 wu-sheng 提交于
-
由 Brandon Fergerson 提交于
* refactor: make more consistent * refactor: make more consistent Co-authored-by:
吴晟 Wu Sheng <wu.sheng@foxmail.com>
-
- 09 8月, 2022 6 次提交
-
-
由 wu-sheng 提交于
-
由 Wan Kai 提交于
Support Elasticsearch column alias for the compatibility between storage logicSharding model and no-logicSharding model. (#9442) ## New ElasticSearch storage option explanation in 9.2.0 Since v9.2.0, SkyWalking OAP provides 2 storage options for metrics/meter and records, system environment variable is (`SW_STORAGE_ES_LOGIC_SHARDING`): ### No-Sharding Model (OAP default setting, `SW_STORAGE_ES_LOGIC_SHARDING = false`) 1. OAP merges all metrics/meter and records(without super datasets, such as segments) indices into one physical index template `metrics-all` and `records-all`. 2. The logic index name would be present in columns `metric_table` and `record_table`. 3. If the logic column name has an alias (configured by `@ElasticSearch.Column()`), the alias would be the real physical column name. ### No-Sharding Model (`SW_STORAGE_ES_LOGIC_SHARDING = true `) 1. OAP shard metrics/meter indices into multi-physical indices as in the previous versions(one index template per metric/meter aggregation function). 2. Records and metrics without configuring aggregation function in `@MetricsFunction` and `@MeterFunction` would not be sharded. 3. The shard template name would be `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`. 4. The OAP **would not** use the column alias, the logic column name would be the real physical column name. **Notice**: Users still could choose to adjust ElasticSearch's shard number(`SW_STORAGE_ES_INDEX_SHARDS_NUMBER`) to scale out no matter the option.
-
由 wu-sheng 提交于
-
由 Brandon Fergerson 提交于
-
由 Brandon Fergerson 提交于
-
由 wu-sheng 提交于
Move the forcedly flush out of each worker's #flush, which would only make the left data flushing into the storage ASAP. In my previous fix, it would increase the number of flushing as the number of workers, which is unnecessary too.
-
- 08 8月, 2022 2 次提交
-
-
由 wu-sheng 提交于
[Critical] Fix a low-performance issue of metrics persistent in the ElasticSearch storage implementation. One single metric could have to wait for an unnecessary 7~10s(System Env Variable SW_STORAGE_ES_FLUSH_INTERVAL). This is a solid and critical performance issue, from the self-observability metric, we could find one metric that would need 7-10s to execute the data flush, which is not expected.
-
由 Fine0830 提交于
-
- 07 8月, 2022 1 次提交
-
-
由 Fine0830 提交于
-
- 06 8月, 2022 1 次提交
-
-
由 静夜思朝颜 提交于
-
- 05 8月, 2022 1 次提交
-
-
由 静夜思朝颜 提交于
Elasticsearch storage support merge all records(without super datasets) indices into one physical index (#9424)
-
- 04 8月, 2022 1 次提交
-
-
由 Wan Kai 提交于
-
- 03 8月, 2022 1 次提交
-
-
由 Wan Kai 提交于
-
- 01 8月, 2022 1 次提交
-
-
由 StreamLang 提交于
-
- 29 7月, 2022 3 次提交
- 28 7月, 2022 3 次提交
- 27 7月, 2022 2 次提交
- 26 7月, 2022 1 次提交
-
-
由 xiao ru xing 提交于
Signed-off-by: Nxiaorx <xiaorx@asiainfo.com>
-
- 25 7月, 2022 1 次提交
-
-
由 wu-sheng 提交于
-
- 21 7月, 2022 2 次提交
-
-
由 kezhenxu94 提交于
-
由 kezhenxu94 提交于
-
- 20 7月, 2022 1 次提交
-
-
由 Brandon Fergerson 提交于
-
- 19 7月, 2022 1 次提交
-
-
由 Fine0830 提交于
-
- 18 7月, 2022 1 次提交
-
-
由 Wan Kai 提交于
-
- 14 7月, 2022 2 次提交
- 13 7月, 2022 4 次提交
-
-
由 Fine0830 提交于
-
由 静夜思朝颜 提交于
-
由 kezhenxu94 提交于
UI templates are configurable, users might add or remove configs as they want, so we don't need to throw exception for inexistent paths, this allow users to remove templates they don't want, or even disable the `ui_template` index.
-
由 wu-sheng 提交于
* Revert #8066 * Update changelog
-
- 12 7月, 2022 1 次提交
-
-
由 wu-sheng 提交于
-
- 09 7月, 2022 1 次提交
-
-
由 kezhenxu94 提交于
-
- 08 7月, 2022 1 次提交
-
-
由 Fine0830 提交于
-