b635e254c4
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.
|
||
|---|---|---|
| .github | ||
| .mvn/wrapper | ||
| apm-application-toolkit | ||
| apm-checkstyle | ||
| apm-commons | ||
| apm-dist | ||
| apm-dist-es7 | ||
| apm-protocol | ||
| apm-sniffer | ||
| apm-webapp | ||
| dist-material | ||
| docker | ||
| docs | ||
| install | ||
| licenses | ||
| oap-server | ||
| skywalking-ui@86ed033a6f | ||
| test | ||
| tools | ||
| .asf.yaml | ||
| .gitignore | ||
| .gitmodules | ||
| CHANGES.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| HEADER | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| codeStyle.xml | ||
| lombok.config | ||
| mvnw | ||
| mvnw.cmd | ||
| pom.xml | ||
README.md
Apache SkyWalking
SkyWalking: an APM(application performance monitor) system, especially designed for microservices, cloud native and container-based (Docker, Kubernetes, Mesos) architectures.
Abstract
SkyWalking is an open source APM system, including monitoring, tracing, diagnosing capabilities for distributed system in Cloud Native architecture. The core features are following.
- Service, service instance, endpoint metrics analysis
- Root cause analysis. Profile the code on the runtime. Read Apache SkyWalking: Use Profiling to Fix the Blind Spot of Distributed Tracing.
- Service topology map analysis
- Service, service instance and endpoint dependency analysis
- Slow services and endpoints detected
- Performance optimization
- Distributed tracing and context propagation
- Database access metrics. Detect slow database access statements(including SQL statements).
- Alarm
SkyWalking supports to collect telemetry (traces and metrics) data from multiple sources and multiple formats, including
- Java, .NET Core, NodeJS and PHP auto-instrument agents.
- Go agent.
- LUA agent, especially for Nginx, OpenResty.
- Service Mesh Observability, including Envoy gRPC Access Log Service (ALS) format in Istio controlled service mesh, Istio telemetry.
- Metrics system, including Prometheus, Spring Sleuth(Micrometer).
- Zipkin v1/v2 and Jaeger gRPC format with limited topology and metrics analysis.(Experimental).
Document
NOTICE, SkyWalking 8.0+ uses v3 protocols. They are incompatible with previous released.
Downloads
Please head to the releases page to download a release of Apache SkyWalking.
Code of conduct
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please follow the REPORTING GUIDELINES to report unacceptable behavior.
Live Demo
Host in Beijing. Go to demo.
Video on youtube.com
Screenshot
| Dashboard | |
 |
 |
| Topology Map | Trace |
 |
 |
Compiling project
Follow this document.
Contact Us
- Mail list: dev@skywalking.apache.org. Mail to
dev-subscribe@skywalking.apache.org, follow the reply to subscribe the mail list. - Join
skywalkingchannel at Apache Slack. If the link is not working, find the latest one at Apache INFRA WIKI. - Twitter, ASFSkyWalking
- QQ Group: 901167865(Recommended), 392443393
- bilibili B站 视频
Who Uses SkyWalking?
Hundreds of companies and organizations use SkyWalking for research, production, and commercial product.
The PoweredBy page includes more users of the project. Users are encouraged to add themselves to there.
Landscapes
SkyWalking enriches the CNCF CLOUD NATIVE Landscape.
Our project enriches the OpenAPM Landscape!