This is an automated email from the ASF dual-hosted git repository.
wusheng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/skywalking.git
The following commit(s) were added to refs/heads/master by this push:
new 8dfd18ec20 fix: correct system variable spelling (#9968)
8dfd18ec20 is described below
commit 8dfd18ec20565a19fa0a1192bc6aa1902354fccb
Author: Brandon Fergerson <[email protected]>
AuthorDate: Wed Nov 16 12:21:34 2022 +0400
fix: correct system variable spelling (#9968)
---
docs/en/changes/changes.md | 1 +
docs/en/setup/backend/configuration-vocabulary.md | 2 +-
docs/en/setup/backend/endpoint-grouping-rules.md | 2 +-
oap-server/server-starter/src/main/resources/application.yml | 2 +-
.../server-tools/data-generator/src/main/resources/application.yml | 2 +-
5 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/docs/en/changes/changes.md b/docs/en/changes/changes.md
index 008b3feb94..27e3a79a66 100644
--- a/docs/en/changes/changes.md
+++ b/docs/en/changes/changes.md
@@ -110,6 +110,7 @@
* Bump up Kafka client to 2.8.1 to fix CVE-2021-38153.
* Remove `lengthEnvVariable` for `Column` as it never works as expected.
* Add `LongText` to support longer logs persistent as a text type in
ElasticSearch, instead of a keyword, to avoid length limitation.
+* Fix wrong system variable name
`SW_CORE_ENABLE_ENDPOINT_NAME_GROUPING_BY_OPENAPI`. It was **opaenapi**.
#### UI
diff --git a/docs/en/setup/backend/configuration-vocabulary.md
b/docs/en/setup/backend/configuration-vocabulary.md
index f5ebb4c2c5..d2474336aa 100644
--- a/docs/en/setup/backend/configuration-vocabulary.md
+++ b/docs/en/setup/backend/configuration-vocabulary.md
@@ -46,7 +46,7 @@ The Configuration Vocabulary lists all available
configurations provided by `app
| - | - | maxPageSizeOfQueryProfileSnapshot
| The maximum size for
snapshot analysis in an OAP query.
[...]
| - | - | maxSizeOfAnalyzeProfileSnapshot
| The maximum number of
snapshots analyzed by the OAP.
[...]
| - | - | prepareThreads
| The number of threads
used to prepare metrics data to the storage.
[...]
-| - | - |
enableEndpointNameGroupingByOpenapi
| Automatically groups endpoints by the given OpenAPI definitions.
[...]
+| - | - |
enableEndpointNameGroupingByOpenapi
| Automatically groups endpoints by the given OpenAPI definitions.
[...]
| - | - |
maxDurationOfQueryEBPFProfilingData
| The maximum duration(in second) of query the eBPF profiling data
from database.
[...]
| - | - |
maxThreadCountOfQueryEBPFProfilingData
| The maximum thread count of query the eBPF profiling data from
database.
[...]
| cluster | standalone | -
| Standalone is not
suitable for running on a single node running. No configuration available.
[...]
diff --git a/docs/en/setup/backend/endpoint-grouping-rules.md
b/docs/en/setup/backend/endpoint-grouping-rules.md
index a6e2d581ca..6253dd4ba5 100644
--- a/docs/en/setup/backend/endpoint-grouping-rules.md
+++ b/docs/en/setup/backend/endpoint-grouping-rules.md
@@ -58,7 +58,7 @@ info:
│ └── serviceB
│ └── productAPI-v2.yaml
```
-3. The feature is enabled by default. You can disable it by setting the `Core
Module` configuration
`${SW_CORE_ENABLE_ENDPOINT_NAME_GROUPING_BY_OPAENAPI:false}`.
+3. The feature is enabled by default. You can disable it by setting the `Core
Module` configuration
`${SW_CORE_ENABLE_ENDPOINT_NAME_GROUPING_BY_OPENAPI:false}`.
### Rules match priority
We recommend designing the API path as clearly as possible. If the API path is
fuzzy and an endpoint name matches multiple paths, SkyWalking would select a
path according to the match priority set out below:
diff --git a/oap-server/server-starter/src/main/resources/application.yml
b/oap-server/server-starter/src/main/resources/application.yml
index bc3af91b94..3e8329abac 100644
--- a/oap-server/server-starter/src/main/resources/application.yml
+++ b/oap-server/server-starter/src/main/resources/application.yml
@@ -131,7 +131,7 @@ core:
# The number of threads used to prepare metrics data to the storage.
prepareThreads: ${SW_CORE_PREPARE_THREADS:2}
# Turn it on then automatically grouping endpoint by the given OpenAPI
definitions.
- enableEndpointNameGroupingByOpenapi:
${SW_CORE_ENABLE_ENDPOINT_NAME_GROUPING_BY_OPAENAPI:true}
+ enableEndpointNameGroupingByOpenapi:
${SW_CORE_ENABLE_ENDPOINT_NAME_GROUPING_BY_OPENAPI:true}
storage:
selector: ${SW_STORAGE:h2}
elasticsearch:
diff --git
a/oap-server/server-tools/data-generator/src/main/resources/application.yml
b/oap-server/server-tools/data-generator/src/main/resources/application.yml
index 4e8a3e7dd1..8da39093cb 100755
--- a/oap-server/server-tools/data-generator/src/main/resources/application.yml
+++ b/oap-server/server-tools/data-generator/src/main/resources/application.yml
@@ -76,7 +76,7 @@ core:
# The number of threads used to prepare metrics data to the storage.
prepareThreads: ${SW_CORE_PREPARE_THREADS:2}
# Turn it on then automatically grouping endpoint by the given OpenAPI
definitions.
- enableEndpointNameGroupingByOpenapi:
${SW_CORE_ENABLE_ENDPOINT_NAME_GROUPING_BY_OPAENAPI:true}
+ enableEndpointNameGroupingByOpenapi:
${SW_CORE_ENABLE_ENDPOINT_NAME_GROUPING_BY_OPENAPI:true}
storage:
selector: ${SW_STORAGE:h2}
elasticsearch:
