- 06 12月, 2020 1 次提交
-
-
由 osiriswd 提交于
-
- 26 11月, 2020 1 次提交
-
-
由 Gao Hongtao 提交于
-
- 25 11月, 2020 1 次提交
-
-
由 Gao Hongtao 提交于
* Add Istio control plane otel MAL expressions and UI template * Remove OpenCensus receiver, add OpenTelemetry receiver * Transfer oc receiver to ot receiver * Create indices on boot * Document istio metrics and otel receiver * Update CHANGES.md * Fix potential NPE * Add group to meter and cleanup istio mixer * Update e2e case due to the change of meter metric name * Update prometheus fetcher config, fix sql builder issue of h2 * Disable istio and so11y metrics by default. * Fix micrometer testcase
-
- 01 11月, 2020 1 次提交
-
-
由 zifeihan 提交于
* 1.Add ThreadPoolExecutor for handle kafka message. Co-authored-by: NDaming <zteny@foxmail.com> Co-authored-by: 吴晟 Wu Sheng <wu.sheng@foxmail.com>
-
- 21 10月, 2020 1 次提交
-
-
由 Gao Hongtao 提交于
-
- 05 9月, 2020 1 次提交
-
-
由 Gao Hongtao 提交于
* Support SSL for prometheus telemetry and prometheus fetcher * Documents * Clear up abandunt dependencies * Update license Signed-off-by: NGao Hongtao <hanahmily@gmail.com> Co-authored-by: 吴晟 Wu Sheng <wu.sheng@foxmail.com>
-
- 04 9月, 2020 1 次提交
-
-
由 Gao Hongtao 提交于
-
- 03 8月, 2020 1 次提交
-
-
由 Daming 提交于
-
- 30 7月, 2020 1 次提交
-
-
由 Daming 提交于
-
- 08 6月, 2020 1 次提交
-
-
由 Gao Hongtao 提交于
-
- 24 4月, 2020 1 次提交
-
-
由 wu-sheng 提交于
Here are the basic and simple usages of the MeterSystem APIs. ## Meter Creation New meter could be created based on metrics name, function, scope and data type. 1. Metrics name is still the storage entity name. 2. Functions are every similar with the OAL function, just accepting different input. ```java final MeterSystem meterSystem = MeterSystem.meterSystem(getManager()); meterSystem.create("test_long_metrics", "avg", ScopeType.SERVICE, Long.class); ``` NOTICE, this creation should only be called in the `module#prepare` stage, otherwise, `Can't create new metrics anymore` exception will be raised after the **CORE** module `start` stage finished. You may find out, there is a chance `create` could be executed successfully in your own `module#start` stage, but it it just because of the sequence of provider loaded by the class loader, **no guarantee, so please don't do that**. ## Runtime Calculation `AcceptableValue` is the object created at the runtime to accept new metrics value. ```java final MeterSystem service = getManager().find(CoreModule.NAME).provider().getService(MeterSystem.class); Executors.newSingleThreadScheduledExecutor().scheduleAtFixedRate(new Runnable() { @Override public void run() { final AcceptableValue<Long> value = service.buildMetrics("test_long_metrics", Long.class); value.accept(MeterEntity.newService("abc"), 5L); value.setTimeBucket(TimeBucket.getMinuteTimeBucket(System.currentTimeMillis())); service.doStreamingCalculation(value); } }, 2, 2, TimeUnit.SECONDS); ``` ## Meter Functions Right now, only `avg` function has been implemented. I submit this PR as soon as possible to get your feedback. I will add more functions. ## Notice 1. Make slow trace query available in the sampled record. Logically, they are the same thing. The UI doesn't need to concern about the trace as a special case. 2. Endpoint dependency will be removed from the dashboard. Because no query available for it. We will provide a new page for that in 8.1 3. Comparison page will be removed due to dashboard is powerful enough to replace it.
-