- 04 9月, 2022 1 次提交
-
-
由 Lv Lifeng 提交于
-
- 02 9月, 2022 1 次提交
-
-
由 DamonXue(Fibonacci) 提交于
-
- 01 9月, 2022 1 次提交
-
-
由 kezhenxu94 提交于
-
- 31 8月, 2022 2 次提交
-
-
由 kezhenxu94 提交于
-
由 wu-sheng 提交于
* [maven-release-plugin] prepare release v9.2.0 * [maven-release-plugin] prepare for next development iteration * Create changes-9.2.0.md * Update changes.md * Update LICENSE
-
- 30 8月, 2022 3 次提交
-
-
由 静夜思朝颜 提交于
-
由 静夜思朝颜 提交于
-
由 xiao ru xing 提交于
-
- 29 8月, 2022 1 次提交
-
-
由 静夜思朝颜 提交于
-
- 27 8月, 2022 2 次提交
-
-
由 pg.yang 提交于
-
由 kezhenxu94 提交于
-
- 25 8月, 2022 2 次提交
-
-
由 kezhenxu94 提交于
-
由 Fine0830 提交于
-
- 24 8月, 2022 3 次提交
- 23 8月, 2022 1 次提交
-
-
由 yswdqz 提交于
-
- 22 8月, 2022 3 次提交
-
-
由 Fine0830 提交于
-
由 kezhenxu94 提交于
-
由 yswdqz 提交于
-
- 21 8月, 2022 3 次提交
-
-
由 kezhenxu94 提交于
-
由 kezhenxu94 提交于
-
由 kezhenxu94 提交于
-
- 20 8月, 2022 3 次提交
-
-
由 Tomasz Pytel 提交于
-
由 kezhenxu94 提交于
Add Kubernetes support module to share codes between modules and reduce calls to Kubernetes API server (#9493)
-
由 Tomasz Pytel 提交于
* component IDs for AWS Lambda Functions plugins * add AsyncPG and AIORedis components
-
- 18 8月, 2022 2 次提交
- 16 8月, 2022 1 次提交
-
-
由 Wan Kai 提交于
Optimize TTL mechanism for Elasticsearch storage, skip executed indices in one TTL rotation. (#9473) * Optimize TTL mechanism for Elasticsearch storage, skip executed indices in one TTL rotation * remove inspect
-
- 15 8月, 2022 1 次提交
-
-
由 静夜思朝颜 提交于
-
- 14 8月, 2022 1 次提交
-
-
由 Brandon Fergerson 提交于
-
- 12 8月, 2022 3 次提交
- 10 8月, 2022 3 次提交
-
-
由 pg.yang 提交于
-
由 wu-sheng 提交于
-
由 Brandon Fergerson 提交于
* refactor: make more consistent * refactor: make more consistent Co-authored-by: 吴晟 Wu Sheng <wu.sheng@foxmail.com>
-
- 09 8月, 2022 3 次提交
-
-
由 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 提交于
-