Fix typo in concepts and designs doc (#9385)

Signed-off-by: xiaorx <xiaorx@asiainfo.com>
This commit is contained in:
xiao ru xing 2022-07-26 12:05:05 +08:00 committed by GitHub
parent bb8f9e1f38
commit 67bb7c4083
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 5 additions and 5 deletions

View File

@ -107,7 +107,7 @@ filter {
- `grok` (TODO)
We're aware of certains performance issues in the grok Java library, and so we're currently conducting investigations and benchmarking. Contributions are
We're aware of certain performance issues in the grok Java library, and so we're currently conducting investigations and benchmarking. Contributions are
welcome.
### Extractor
@ -359,7 +359,7 @@ filter {
sampler {
// ... sampler configs
}
if (parserd.level == "ERROR" || parsed.userId == "TestingUserId") { // sample error logs or testing users' logs (userId == "TestingUserId") even if the sampling strategy is configured
if (parsed.level == "ERROR" || parsed.userId == "TestingUserId") { // sample error logs or testing users' logs (userId == "TestingUserId") even if the sampling strategy is configured
enforcer {
}
}

View File

@ -21,7 +21,7 @@ On a high level, there are four typical categories in all SkyWalking probes.
span data. See
[Receiver for Zipkin traces](../setup/backend/zipkin-trace.md) for more information.
- **eBPF agent**. The eBPF agent collects metrics and proifiling the target service powered by the eBPF technology of Linux kernel.
- **eBPF agent**. The eBPF agent collects metrics and profiling the target service powered by the eBPF technology of Linux kernel.
You don't need to use **Language based native agent** and **Service Mesh probe** at the same time, since they both serve
to collect metrics data. Otherwise, your system will suffer twice the payload, and the analytic numbers will be doubled.

View File

@ -87,7 +87,7 @@ threadPool.submit(new Task2(countDownLatch));
try {
countDownLatch.await(500, TimeUnit.MILLISECONDS);
} catch (InterruptedExceptione) {
} catch (InterruptedException) {
}
```

View File

@ -65,7 +65,7 @@ Since version 6.3.0, we have introduced more automatic tests to perform software
The E2E test involves some/all of the OAP server, storage, coordinator, webapp, and the instrumented services, all of which are orchestrated by `docker-compose` or `KinD`.
Since version 8.9.0, we immigrate to e2e-v2 which leverage [skywalking-infra-e2e](https://github.com/apache/skywalking-infra-e2e) and [skywalking-cli](https://github.com/apache/skywalking-cli) to do the whole e2e process.
`skywalking-infra-e2e` is used to control the e2e process and `skywalking-cli` is used to interact with the OAP such as request and get response metris from OAP.
`skywalking-infra-e2e` is used to control the e2e process and `skywalking-cli` is used to interact with the OAP such as request and get response metrics from OAP.
#### Writing E2E Cases