* Add annotation(AlarmCore.start)
* Upgrade nacos version to 1.2.0
* Revert "Upgrade nacos version to 1.2.0"
This reverts commit 4d7b06f6d20ee09ad377ad6ef736aeab429314e0.
* Update nacos version to 1.2.0(Solve the security problem of the old version of fastsjon)
* Recovery annotation
* Recovery annotation
* Update nacos version to 1.2.0
* Update tls_key_generate.sh path
Update tls_key_generate.sh path
* Add annotation(AlarmCore.start)
* Revert "Upgrade nacos version to 1.2.0"
This reverts commit 4d7b06f6d20ee09ad377ad6ef736aeab429314e0.
* Update nacos version to 1.2.0(Solve the security problem of the old version of fastsjon)
* Recovery annotation
* Recovery annotation
* Update tls_key_generate.sh path
* Execution Authority
* Remove nacos
* remove nacos code
* remove nacos
remove nacos
* remove nacos
remove nacos
* remove nacos
* remove nacos
Co-authored-by: songzhendong <289505773@qq.com>
Co-authored-by: songzhendong <songzhendong@xiaomi.com>
Co-authored-by: 吴晟 Wu Sheng <wu.sheng@foxmail.com>
* Support service relation and database access alarm
* support service instance relation alarm
* support endpoint relation alarm
* document and format the name
* resolve issues
* add database access and endpoint relation rule example
* resolve code format
* remove unnecessary getter and setter package declare
* remove unnecessary fields
Co-authored-by: Mrproliu <mrproliu@lagou.com>
* Add Mariadb JDBC plugin and provide tests
* Refactor component name
* Reformat plugin description and remove healthcheck span from the test
Co-authored-by: Efe Kaptan <Efe.Kaptan@webtrekk.com>
Co-authored-by: zhang-wei <pknfe@outlook.com>
Co-authored-by: 吴晟 Wu Sheng <wu.sheng@foxmail.com>
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.
Daming
Ax1an
吴晟 Wu Sheng
mrproliu
Jared Tan
songzhendong
Evan
xin
Gao Hongtao
wangwei
killGC
caoyixiong
gongdewei
dagmom
于玉桔
xiaoyu
Xin,Zhang
Efe Kaptan
kezhenxu94
innerpeacez
J-Cod3r