Skip to content

S
SkyWalking

apache / SkyWalking
上一次同步 1 年多

通知 302
Star 21345
Fork 6091
S
SkyWalking

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 20 5月, 2020 1 次提交
    • wu-sheng's avatar
      Group Parameterized Endpoints (#4802) · a10e0449
      由 wu-sheng 提交于 
      * Group Parameterized Endpoints. Configure the grouping rules for parameterized endpoints, to improve the meaning of the metrics.
      a10e0449
  3. 14 5月, 2020 1 次提交
  5. 13 5月, 2020 1 次提交
  7. 12 5月, 2020 2 次提交
  9. 11 5月, 2020 1 次提交
    • 静夜思朝颜's avatar
      Alarm support multiple scope (#4769) · 749af3e0
      由 静夜思朝颜 提交于 
      * 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: NMrproliu <mrproliu@lagou.com>
      749af3e0
  11. 09 5月, 2020 1 次提交
  13. 08 5月, 2020 3 次提交
  15. 07 5月, 2020 2 次提交
  17. 29 4月, 2020 2 次提交
  19. 27 4月, 2020 1 次提交
  21. 26 4月, 2020 1 次提交
  23. 25 4月, 2020 3 次提交
  25. 24 4月, 2020 1 次提交
    • wu-sheng's avatar
      Provide Meter(metrics) system (#4694) · b635e254
      由 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.
      b635e254
  27. 23 4月, 2020 1 次提交
  29. 14 4月, 2020 1 次提交
  31. 13 4月, 2020 1 次提交
  33. 12 4月, 2020 2 次提交
  35. 10 4月, 2020 2 次提交
    • wu-sheng's avatar
      Set up restrict length rules for service, instance and endpoint (#4633) · 44cae97c
      由 wu-sheng 提交于 
      * Set up restrict length rules for service, instance and endpoint

* Adjust two env names.
      44cae97c
    • wu-sheng's avatar
      Make 8.0.0 Core available. New protocol and register removed. (#4599) · 6fe2041b
      由 wu-sheng 提交于 
      Here are the list of changes we made in this pull request. Top 3 are the principle changes, others are following these principles.
1. New agent and mesh report protocol. 
2. New agent header protocol. 
3. Service register, instance register and network address register have been removed permanently.
4. Service traffic, instance traffic and network alias metrics are added to replace the service, instance and network address inventory.
5. Register process has been removed.
6. Metrics stream process supports insert only mode, especially for traffic entities.
7. Metrics stream process supports no-downsampling mode for traffic entities and network alias.
8. Remove all register mechanism and cache in the java agent.
9. Remove MONTH step in GraphQL query.
10. Update UI to remove MONTH step query, the max query range is 60 days now.
11. Simplify the TTL to metrics and record. And the unit has been formatted in Day unit. No specific TTL for ElasticSearch storage.
12. Buffer mechanism of trace receiver and mesh receiver has been removed due to no register.
13. New service id, instance id and endpoint id rules, including service relation, instance relation and endpoint relation id rules.
14. Java agent support `keep tracing` mode, meaning, agent generating tracing context even the backend is unconnected/unavailable.
15. Plugin test tool up to date, in order to support new protocol.
16. Plugin tests expected data files updated.
17. E2E tests updated.
18. Telemetry of Grafana config has been merged into one.
19. Documentation updates.
20. [TBD] InfluxDB storage implementation is not available, need @dmsolr to fix later, in order to reduce the master change block by this PR.
      6fe2041b
  37. 08 4月, 2020 1 次提交
  39. 31 3月, 2020 1 次提交
  41. 28 3月, 2020 1 次提交
    • wu-sheng's avatar
      [Inventory Design Change] Remove endpoint register and endpoint inventory (#4570) · 4474907f
      由 wu-sheng 提交于 
      * Finish step one, source and entity changed.

* Step 2, finish the basic and core DAO changes.

* Step 3. Change all source codes of backend, and make project compiling successfully.

* Make startup successful and persistence works.

* Fix dead codes in the MySQLTableInstaller.

* Fix mischange.

* Fix MySQL storage bootstrap error.

* Rollback dependency change.

* Simply enable tailing logs from container no mater it's in CI or not

* Fix segment table issue.

* Fix MySQL Instanller.

* Support Influxdb implementation of new endpoint traffic.

* Set and modify timeout to 90mins

* Remove unnecessary entity in the EndpointTraffic.

* Fix wrong entity builder and make name more clear.

* Fix 2 equal methods bug.

* Fix InfluxDB identifier(name) conflict issue.

* Fix endpoint topology query, endpoint id should be changed as a string.

* Fix a missing change.

* Fix a wrong commit.

* Column name can't be changed, due to it affect the hybrid metadb(h2/mysql) query, change it explicitly with double quotation marks.

* Fix formats.

* Remove endpoint/operation register from the agent. and change the plugin tests(without local tests). operationId relation codes have been removed from agent too.

* Try to fix the hytrix case.

* Fix 3 cases.

* Try to fix cases.

* Fix 2.

* Fix one.

* Fix the serviceId type mis-change.

* Fix int query

* Fix hystrix case.

* Fix a case.

* Fix EndpointCallRelationDispatcher set the source/dest endpoint without id encoding.

* Update documentation and add 2 test cases.
Co-authored-by: Nkezhenxu94 <kezhenxu94@163.com>
      4474907f
  43. 27 3月, 2020 2 次提交
    • Indifer's avatar
      fix elasticsearch-5.x-plugin when use es6.x TransportClient error (#4517) · 1bc40828
      由 Indifer 提交于 
      * up ui

* up ui

* fix elasticsearch-5.x-plugin on es6.x TransportClient error, Found class org.elasticsearch.common.transport.TransportAddress, but interface was expected
up elasticsearch-6.x-plugin support TransportClient

* fix elasticsearch-5.x-plugin on es6.x TransportClient error, Found class org.elasticsearch.common.transport.TransportAddress, but interface was expected
up elasticsearch-6.x-plugin support TransportClient

* fix elasticsearch-5.x-plugin on es6.x TransportClient error, Found class org.elasticsearch.common.transport.TransportAddress, but interface was expected
up elasticsearch-6.x-plugin support TransportClient

* const string witnesses
add some unit test
recommended to change ; to ,

* const string witnesses
add some unit test
recommended to change ; to ,

* up ES6.X test-plugin

* up es6.x test-plugin

* up es6.x test-plugin

* up es6.x test-plugin

* add DeleteIndexRequest

* up es6.x test-plugin

* remove TransportCaseController.java

* fix TransportActionNodeProxyExecuteMethodsInterceptorTest
Co-authored-by: Nyi.liang <yi.liang@zhangmen.cn>
Co-authored-by: wu-sheng's avatar吴晟 Wu Sheng <wu.sheng@foxmail.com>
Co-authored-by: N梁懿 <liangyi@xforceplus.com>
Co-authored-by: Naderm <394102339@qq.com>
      1bc40828
    • R
      Syntax, grammar and basic cleanup. (#4575) · a45fb308
      由 Randy Abernethy 提交于 
      Co-authored-by: wu-sheng's avatar吴晟 Wu Sheng <wu.sheng@foxmail.com>
      a45fb308
  45. 26 3月, 2020 2 次提交
  47. 25 3月, 2020 1 次提交
  49. 24 3月, 2020 2 次提交
  51. 23 3月, 2020 2 次提交
  53. 20 3月, 2020 1 次提交