- 30 7月, 2021 1 次提交
-
-
由 wu-sheng 提交于
* [maven-release-plugin] prepare release v8.7.0 * [maven-release-plugin] prepare for next development iteration
-
- 08 6月, 2021 1 次提交
-
-
由 wu-sheng 提交于
-
- 09 4月, 2021 1 次提交
-
-
由 wu-sheng 提交于
-
- 02 2月, 2021 1 次提交
-
-
由 wu-sheng 提交于
* [maven-release-plugin] prepare release v8.4.0 * [maven-release-plugin] prepare for next development iteration
-
- 29 11月, 2020 1 次提交
-
-
由 wu-sheng 提交于
* [maven-release-plugin] prepare release v8.3.0 * [maven-release-plugin] prepare for next development iteration
-
- 24 10月, 2020 1 次提交
-
-
由 kezhenxu94 提交于
* [maven-release-plugin] prepare release v8.2.0 * [maven-release-plugin] prepare for next development iteration
-
- 31 7月, 2020 1 次提交
-
-
由 wu-sheng 提交于
* [maven-release-plugin] prepare release v8.1.0 * [maven-release-plugin] prepare for next development iteration
-
- 30 7月, 2020 1 次提交
-
-
由 Daming 提交于
-
- 12 6月, 2020 1 次提交
-
-
由 wu-sheng 提交于
* [maven-release-plugin] prepare release v8.0.0 * [maven-release-plugin] prepare for next development iteration * Remove all shardingsphere cases.
-
- 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.
-
- 16 3月, 2020 1 次提交
-
-
由 kezhenxu94 提交于
Motivation: According the feedback from the community, the e2e tests are hard for them to understand and get them started, so this pull request aims to rewrite the e2e tests with some improvements: - debuggable locally, now you can run every individual case directly inside the IDE, just like running a plain unit test. - same functionalities of multiple counterparts share the same codes, cases like different storages and cluster coordinators share the same codes, easy to add more similar cases. - the "end" now extends to the Doccker images, meaning that some bugs like #4483 and #4471 can be more easily and early to be discovered. - codes style and license headers are checked Modifications: - adopt jupeter (a.k.a junit 5), testcontainers as the new test framework, all containers are orchestrated by docker-compose.yml, well-known technology that developers should be familiar with. - rewrite all test cases and verify them. - reorganize the workflows in GitHub Actions. Result: - new e2e test should be easy to add. - closes https://github.com/apache/skywalking/issues/4472
-
- 19 2月, 2020 1 次提交
-
-
由 Daming 提交于
* provide influxdb as a new storage plugin Co-authored-by: Nkezhenxu94 <kezhenxu94@163.com> Co-authored-by:
吴晟 Wu Sheng <wu.sheng@foxmail.com>
-
- 10 9月, 2019 1 次提交
-
-
由 kezhenxu94 提交于
* Add TTL E2E test * Add to Jenkins stage and minor bugfix * Upgrade e2e container version * Polish and minor fix * Polish
-
- 30 8月, 2019 1 次提交
-
-
由 kezhenxu94 提交于
* Support Gateway without agent
-
- 14 7月, 2019 1 次提交
-
-
由 kezhenxu94 提交于
* Add e2e cluster tests
-
- 30 6月, 2019 1 次提交
-
-
由 kezhenxu94 提交于
e2e test setup. cc @hanahmily @peng-yongsheng @IanCao @zhaoyuguang @JaredTan95 # e2e test case One single standalone Spring service, accessing H2 database. This service has been installed the agent. OAP runs in single mode with H2 storage too. The e2e test will verify the results through GraphQL query 1. Traces exist. 2. Service/Service Instance/Endpoint exist and have expected metrics. 3. Topology exists and match expected.
-
- 29 6月, 2019 1 次提交
-
-
由 wu-sheng 提交于
* [maven-release-plugin] prepare release v6.2.0 * [maven-release-plugin] prepare for next development iteration
-
- 30 4月, 2019 1 次提交
-
-
由 wu-sheng 提交于
* Move submodule plugin. * Always auto-submodule * [maven-release-plugin] prepare release v6.1.0 * [maven-release-plugin] prepare for next development iteration * Change keys location.
-
- 18 1月, 2019 1 次提交
-
-
由 wu-sheng 提交于
* [maven-release-plugin] prepare release v6.0.0-GA * [maven-release-plugin] prepare for next development iteration
-
- 23 12月, 2018 1 次提交
-
-
由 wu-sheng 提交于
-
- 06 11月, 2018 1 次提交
-
-
由 wu-sheng 提交于
* Lock oracle and resin plugins version. * Move resin and oracle plugin to openskywalking * Restore submodule active. * Add another submodule active command. * Remove the wrong test cases in release and fix some doc issues. * [maven-release-plugin] prepare release v6.0.0-alpha * [maven-release-plugin] prepare for next development iteration * Fix some doc
-
- 10 10月, 2018 1 次提交
-
-
由 wu-sheng 提交于
-
- 29 8月, 2018 1 次提交
-
-
由 wu-sheng 提交于
-
- 19 7月, 2018 1 次提交
-
-
由 彭勇升 pengys 提交于
* Receiver, aggregate, server finished.
-
- 11 7月, 2018 1 次提交
-
-
由 彭勇升 pengys 提交于
* Cluster module implementation finished.
-
- 07 7月, 2018 1 次提交
-
-
由 peng-yongsheng 提交于
-
- 16 5月, 2018 1 次提交
-
-
由 wu-sheng 提交于
-
- 02 4月, 2018 1 次提交
-
-
由 彭勇升 pengys 提交于
#1009
-
- 14 3月, 2018 1 次提交
-
-
由 wu-sheng 提交于
* [maven-release-plugin] prepare release apm-5.0.0-alpha * [maven-release-plugin] prepare for next development iteration
-
- 26 2月, 2018 1 次提交
-
-
由 wu-sheng 提交于
Fix assmbly for mvn clean install -Papache-release and update version to SNAPSHOT for SNAPSHOT release.
-
- 17 12月, 2017 3 次提交
-
-
由 peng-yongsheng 提交于
-
由 peng-yongsheng 提交于
-
由 peng-yongsheng 提交于
-
- 15 12月, 2017 1 次提交
-
-
由 gaohongtao 提交于
-
- 10 12月, 2017 1 次提交
-
-
由 wu-sheng 提交于
-
- 09 12月, 2017 1 次提交
-
-
由 wu-sheng 提交于
-
- 06 12月, 2017 1 次提交
-
-
由 wu-sheng 提交于
-
- 04 12月, 2017 1 次提交
-
-
由 wu-sheng 提交于
-
- 22 11月, 2017 1 次提交
-
-
由 peng-yongsheng 提交于
-