- 27 11月, 2021 2 次提交
-
-
由 刘威 提交于
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/
-
由 ken-duck 提交于
-
- 26 11月, 2021 2 次提交
-
-
由 刘威 提交于
-
由 Marc Navarro 提交于
Upgrade to the latest grpc-java 1.42.1 which is only compatible and [tested against](https://github.com/grpc/grpc-java/pull/8551#discussion_r714182190) 3.17.2, but we can assume that 3.17.3 (which has osx-aarch_64 compatible maven artifacts) is save to use. We could have also upgrade to the latest grpc-java 1.42.1 and latest protoc 3.19.1, but it can not be directly done, it needs to tweak the grpcs-java internal dependencies. So we choose the safest option and discarded this option because of the following reasons: - Protoc 3.19.1 generates code that relies on methods not available in protobuf-java 3.17.2 ([“issue”](https://github.com/protocolbuffers/protobuf/issues/9236#issue-1059594027)) (which java-grpc relies on). So we need to tell grpc-java via dependency management to use 3.19.1 instead of 3.17.2. Signed-off-by: NMarc Navarro Sonnenfeld <marcnavarro@tetrate.io>
-
- 25 11月, 2021 1 次提交
-
-
由 kezhenxu94 提交于
-
- 24 11月, 2021 2 次提交
- 22 11月, 2021 4 次提交
-
-
由 liqiangz 提交于
-
由 kezhenxu94 提交于
-
由 wankai123 提交于
-
由 Fine0830 提交于
-
- 21 11月, 2021 1 次提交
-
-
由 kezhenxu94 提交于
-
- 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.
-
- 19 11月, 2021 3 次提交
-
-
由 kezhenxu94 提交于
-
由 wu-sheng 提交于
-
由 静夜思朝颜 提交于
* Change `SO11Y` metric `envoy_als_in_count` to calculate the ALS message count.
-
- 17 11月, 2021 2 次提交
-
-
由 kezhenxu94 提交于
-
由 kezhenxu94 提交于
-
- 16 11月, 2021 1 次提交
-
-
由 wu-sheng 提交于
-
- 13 11月, 2021 1 次提交
-
-
由 kezhenxu94 提交于
-
- 11 11月, 2021 1 次提交
-
-
由 Kirs 提交于
-
- 10 11月, 2021 2 次提交
- 09 11月, 2021 2 次提交
-
-
由 King 提交于
-
由 kezhenxu94 提交于
-
- 06 11月, 2021 2 次提交
- 04 11月, 2021 1 次提交
-
-
由 wu-sheng 提交于
Optimize metrics of minute dimensionality persistence, don't save metric of being default value. (#8066) Optimize metrics of minute dimensionality persistence. - The value of metrics, which has declaration of the default value and current value equals the default value logically, the whole row wouldn't be pushed into database. - Add self-observability `metrics_persistence_skipped` metric to measure the number of skipped metrics. - SLA(percent function), Apdex, AvgLong(MAL mostly) metrics are mostly optimized because of this. Such as a full-failing error(0% successful rate) and unhealthy(apdex=0) are not costing the storage. - Hour/Day dimensionalities metrics are not changed, as they cover long duration. - Fix `max` function in OAL doesn't support negative long.
-
- 03 11月, 2021 2 次提交
- 02 11月, 2021 2 次提交
- 01 11月, 2021 2 次提交
- 29 10月, 2021 3 次提交
- 28 10月, 2021 2 次提交
- 27 10月, 2021 1 次提交
-
-
由 Fine0830 提交于
-