- 23 12月, 2021 1 次提交
-
-
由 kezhenxu94 提交于
-
- 06 12月, 2021 1 次提交
-
-
由 wu-sheng 提交于
-
- 02 12月, 2021 1 次提交
-
-
由 wu-sheng 提交于
-
- 30 11月, 2021 1 次提交
-
-
- 29 11月, 2021 1 次提交
-
-
由 静夜思朝颜 提交于
-
- 27 11月, 2021 1 次提交
-
-
由 刘威 提交于
Support Apache IoTDB as a storage option, mostly refer to previous InfluxDB storage option. * The Design of Apache IoTDB Storage Option, https://skywalking.apache.org/blog/2021-11-23-design-of-iotdb-storage-option/
-
- 26 11月, 2021 1 次提交
-
-
由 刘威 提交于
-
- 24 11月, 2021 1 次提交
-
-
由 wu-sheng 提交于
-
- 20 11月, 2021 1 次提交
-
-
由 kezhenxu94 提交于
The ES persistence execution is now asynchronous and the execution latency only counts the time to insert the requests into the bulk processor, instead of the time after the requests are flushed into the storage, this patch fixes that issue. There is the same issue in prepare latency but that needs more changes so I'll leave it to another pull request.
-
- 27 10月, 2021 1 次提交
-
-
由 wu-sheng 提交于
Fix ElasticSearch implementation of `queryMetricsValues` and `readLabeledMetricsValues` doesn't fill default values (#8012) * Fix ElasticSearch implementation of `queryMetricsValues` and `readLabeledMetricsValues` doesn't fill default values * Change generated file path.
-
- 26 10月, 2021 1 次提交
-
-
由 Kirs 提交于
-
- 25 10月, 2021 1 次提交
-
-
由 wu-sheng 提交于
-
- 21 10月, 2021 1 次提交
-
-
由 zhang-wei 提交于
-
- 29 9月, 2021 1 次提交
-
-
由 wu-sheng 提交于
* Revert mis-change, which makes the endpoint dependency breaking. * Update change log.
-
- 28 9月, 2021 1 次提交
-
-
由 kezhenxu94 提交于
-
- 25 9月, 2021 1 次提交
-
-
由 wu-sheng 提交于
* [maven-release-plugin] prepare release v8.8.0 * [maven-release-plugin] prepare for next development iteration * Create changes-8.8.0.md * Reset changelog for 8.9.0
-
- 23 9月, 2021 1 次提交
-
-
由 wu-sheng 提交于
* Only report `bug warning` in precise conditions. * Add a test check for template existing.
-
- 17 9月, 2021 2 次提交
-
-
由 kezhenxu94 提交于
-
由 nicolchen 提交于
-
- 15 9月, 2021 2 次提交
-
-
由 刘威 提交于
* Fix H2EventQueryDAO doesn't sort data by Event.START_TIME. * Fix H2EventQueryDAO uses a wrong pagination query.
-
由 kezhenxu94 提交于
-
- 12 9月, 2021 1 次提交
-
-
由 kezhenxu94 提交于
-
- 11 9月, 2021 1 次提交
-
-
由 刘威 提交于
-
- 08 9月, 2021 1 次提交
-
-
由 wankai123 提交于
-
- 06 9月, 2021 1 次提交
-
-
由 kezhenxu94 提交于
-
- 05 9月, 2021 1 次提交
-
-
由 刘威 提交于
-
- 26 8月, 2021 1 次提交
-
-
由 刘威 提交于
-
- 13 8月, 2021 1 次提交
-
-
由 wu-sheng 提交于
DataCarrier changes a `#consume` API to add properties as a parameter to initialize consumer (#7452)
-
- 12 8月, 2021 1 次提交
-
-
由 wu-sheng 提交于
* Remove page path in the browser log query condition. * Remove endpoint name in the backend log query condition.
-
- 11 8月, 2021 1 次提交
-
-
由 wu-sheng 提交于
* [Break Change] Remove endpoint name in the trace query condition. * Fix a local UT error(MacOS only)
-
- 10 8月, 2021 1 次提交
-
-
由 wu-sheng 提交于
-
- 30 7月, 2021 1 次提交
-
-
由 wu-sheng 提交于
* [maven-release-plugin] prepare release v8.7.0 * [maven-release-plugin] prepare for next development iteration
-
- 27 7月, 2021 2 次提交
- 22 7月, 2021 1 次提交
-
-
由 Ax1an 提交于
-
- 20 7月, 2021 1 次提交
-
-
由 wu-sheng 提交于
Fix bug, the enhanced session could cache the metadata metrics(hot entity) forever. A new timeout mechanism is designed for avoiding this specific case. Optimize this timeout mechanism, make it different for ES(one index per day) and non-ES storage implementation.
-
- 16 7月, 2021 1 次提交
-
-
由 wu-sheng 提交于
Adjust index refresh period as INT(flushInterval * 2/3), it used to be as same as bulk flush period. At the edge case, in low traffic(traffic < bulkActions in the whole period), there is a possible case, 2 period bulks are included in one index refresh rebuild operation, which could cause version conflicts. And this case can't be fixed through core/persistentPeriod as the bulk fresh is not controlled by the persistent timer anymore. This PR should avoid the following exception in the low load case, especially when bulkActions is set larger than the number of a metric type.
-
- 15 7月, 2021 2 次提交
- 14 7月, 2021 1 次提交
-
-
由 wu-sheng 提交于
* Performance: remove the synchronous persistence mechanism from batch ElasticSearch DAO. Because the current enhanced persistent session mechanism, don't require the data queryable immediately after the insert and update anymore. * Performance: share `flushInterval` setting for both metrics and record data, due to `synchronous persistence mechanism` removed. Record flush interval used to be hardcoded as 10s. * Remove `syncBulkActions` in ElasticSearch storage option. * Increase the default bulkActions(env, SW_STORAGE_ES_BULK_ACTIONS) to 5000(from 1000). * Increase the flush interval of ElasticSearch indices to 15s(from 10s) Add these 2 references. According to these, **(same _index, _type and _id) in same bulk will be in order** 1. https://github.com/elastic/elasticsearch/issues/50199 2. https://discuss.elastic.co/t/order-of--bulk-request-operations/98124 Notice, the order of different bulks is not guaranteed by the ElasticSearch cluster. We are going to have the risk of dirty write. But consider we set over 20s period between flush, and index flush period is 10, we should be safe. Recommend 5000 bulk size and 15s flush interval only. The persistent period has been set to 25s.
-