Set the `SW_QUERY_MAX_QUERY_COMPLEXITY` default value to 3000 (#11025)
This commit is contained in:
parent
137fb64888
commit
fb19ec41ac
|
|
@ -32,6 +32,7 @@
|
|||
* Add comment for `docker/.env` to explain the usage.
|
||||
* Fix wrong environment variable name `SW_OTEL_RECEIVER_ENABLED_OTEL_RULES` to right `SW_OTEL_RECEIVER_ENABLED_OTEL_METRICS_RULES`.
|
||||
* Fix instance query in JDBC implementation.
|
||||
* Set the `SW_QUERY_MAX_QUERY_COMPLEXITY` default value to 3000(was 1000).
|
||||
|
||||
#### UI
|
||||
|
||||
|
|
|
|||
|
|
@ -237,7 +237,7 @@ The Configuration Vocabulary lists all available configurations provided by `app
|
|||
| - | - | sampleRate | Sampling rate for receiving trace. Precise to 1/10000. 10000 means sampling rate of 100% by default. | SW_RECEIVER_BROWSER_SAMPLE_RATE | 10000 |
|
||||
| query | graphql | - | GraphQL query implementation. | - | |
|
||||
| - | - | enableLogTestTool | Enable the log testing API to test the LAL. **NOTE**: This API evaluates untrusted code on the OAP server. A malicious script can do significant damage (steal keys and secrets, remove files and directories, install malware, etc). As such, please enable this API only when you completely trust your users. | SW_QUERY_GRAPHQL_ENABLE_LOG_TEST_TOOL | false |
|
||||
| - | - | maxQueryComplexity | Maximum complexity allowed for the GraphQL query that can be used to abort a query if the total number of data fields queried exceeds the defined threshold. | SW_QUERY_MAX_QUERY_COMPLEXITY | 1000 |
|
||||
| - | - | maxQueryComplexity | Maximum complexity allowed for the GraphQL query that can be used to abort a query if the total number of data fields queried exceeds the defined threshold. | SW_QUERY_MAX_QUERY_COMPLEXITY | 3000 |
|
||||
| - | - | enableUpdateUITemplate | Allow user add,disable and update UI template. | SW_ENABLE_UPDATE_UI_TEMPLATE | false |
|
||||
| - | - | enableOnDemandPodLog | Ondemand Pod log: fetch the Pod logs on users' demand, the logs are fetched and displayed in real time, and are not persisted in any kind. This is helpful when users want to do some experiments and monitor the logs and see what's happing inside the service. Note: if you print secrets in the logs, they are also visible to the UI, so for the sake of security, this feature is disabled by default, please set this configuration to enable the feature manually. | SW_ENABLE_ON_DEMAND_POD_LOG | false |
|
||||
| query-zipkin | default | - | This module is for Zipkin query API and support zipkin-lens UI | - | |
|
||||
|
|
|
|||
|
|
@ -389,7 +389,7 @@ query:
|
|||
enableLogTestTool: ${SW_QUERY_GRAPHQL_ENABLE_LOG_TEST_TOOL:false}
|
||||
# Maximum complexity allowed for the GraphQL query that can be used to
|
||||
# abort a query if the total number of data fields queried exceeds the defined threshold.
|
||||
maxQueryComplexity: ${SW_QUERY_MAX_QUERY_COMPLEXITY:1000}
|
||||
maxQueryComplexity: ${SW_QUERY_MAX_QUERY_COMPLEXITY:3000}
|
||||
# Allow user add, disable and update UI template
|
||||
enableUpdateUITemplate: ${SW_ENABLE_UPDATE_UI_TEMPLATE:false}
|
||||
# "On demand log" allows users to fetch Pod containers' log in real time,
|
||||
|
|
|
|||
Loading…
Reference in New Issue