Application Performance Management Plus
Application Performance Management Plus
Document
- Documentation
Application Performance Management PlusUser guideServer monitoringUser guidePlatform settingParameter management
Copy page
Download PDFPlatform setting
Parameter management
Copy pageDownload PDFParameter management
Server-side Monitoring provides workspace-level configuration parameters, including error thresholds, sampling rates, and data encryption. You can configure parameters as needed for your business scenarios. This topic describes the configuration details and application scope of these parameters.
warning
Some parameters support custom settings. In such cases, workspace-level parameter settings have lower priority than custom settings. For example, if sampling rules are configured both in Parameter management and for a specific service, the custom sampling rules configured for the service take effect.
Procedure
- Log in to the Server-side Monitoring console.
- In the left navigation pane, select Platform Setting > Workspace Management to access the workspace management page.
- Find the workspace in the workspace list and click Parameter management in the Actions column on the right side of the list. Configure parameters as required for your business scenario, such as system, probe, storage, and performance profiling settings.
System settings
Currently, error threshold settings are supported. To define error threshold ranges for Satisfied, Normal, and Poor levels, click Modify settings, drag the slider as needed, and click Save.
This parameter primarily affects data statistics in the service topology.
Probe settings
Slow database query settings
Define the threshold for slow queries. The recommended threshold is 500ms. To modify the threshold, click Modify setting, configure a threshold as needed, and click Save.
This parameter primarily affects slow query statistics, for example, the proportion of slow queries in middleware monitoring.
Sampling settings
Configure parameters for custom sampling rules. To do so, click Modify settings, configure sampling parameters (such as Fixed Sampling and Wrong slow sampling) as needed, and click Save. At least one sampling method must be configured. The specific activation logic is as follows:
- If only "Fixed Sampling" is configured, both the APMPlus probe and the apmplus-opentelemetry-collector probe take effect.
- If only "Wrong slow sampling" is configured, the APMPlus probe does not take effect, whereas the apmplus-opentelemetry-collector probe takes effect.
- If both "Fixed Sampling" and "Wrong slow sampling" are configured, only the fixed-sampling configuration applies to the APMPlus probe. Both sampling methods apply to the apmplus-opentelemetry-collector probe, which executes them in sequence.
Sampling method | Description |
Fixed sampling | Trace data sampling is performed based on the custom sampling rate. A value of 0% means all trace data is discarded and not reported. A value of 100% means all trace data is reported without sampling. |
Wrong slow sampling | Data is reported based on the custom lower threshold of trace duration and error sampling rules. All trace data matching the error and slow sampling rules will be reported. tip
|
This parameter primarily affects sampling, for example, the source of samples in trace analysis.
Interface settings
To configure interface-related settings, click Modify settings and set parameters including Path Convergence, List of RPC service interfaces, Invalid Interface Call Filtering, and HTTP Status Code Allowlist. After completing the configuration, click Save.
warning
Modifying Path Convergence or List of RPC service interfaces settings will prevent historical data from being filtered by the new Resource values. Proceed with caution.
- Path normalization
- If this option is enabled, HTTP service interface names are generated according to default URL normalization rules. This process aggregates relative paths by replacing numeric IDs with wildcards "?" while preserving meaningful path information.
warning
- This applies only to HTTP services invoked as servers.
- The maximum length defaults to 24 characters and can be modified per account. To modify the maximum length, contact technical support.
- The default URL normalization rules and examples are as follows:
- If the path section of the URL does not contain any digits, the original string is retained. For example, /api/health-check remains /api/health-check after path normalization.
- If the path section of the URL contains digits and the length of segments containing these digits is 2 or 3 characters, the version segments starting with v or V are retained, and the segments containing digits other than version numbers are replaced entirely with the wildcard "?". For example, /v1/items/123 will be /v1/items/? after path normalization.
- If the path section of the URL contains digits and the segments containing digits are from 4 to the maximum length, the digit-containing segments are replaced with the wildcard "?". For example, /api/users/name-456/details will be /api/users/?/details after path normalization.
- If the path section of the URL contains digits and the length exceeds the maximum length, the digit-containing segments are replaced with the wildcard "?". For example, /api/very-long-resource-name-1234567890 will be /api/? after path normalization.
- List of RPC service interfaces
- The source of assignment for RPC service-related interface names. The default option is the method level. You can select the method level or the service method level as needed.
- Method level: The Resource field is assigned by rpc.method.
- Service method level: The Resource field is assigned by rpc.service and rpc.method.
- This parameter primarily affects the interface names of RPC services in interface monitoring.
- Invalid interface call filtering
- Mark interfaces for which you do not need to record observability data as inactive. After this setting takes effect, inactive interfaces will no longer report trace data, and the corresponding metric statistics will exclude data from these interfaces, including spans and metric statistics.
- Data impact: All metrics and spans corresponding to these interfaces are ignored.
- Functional impact: All metrics for the corresponding interfaces on pages such as service overview, interface monitoring, upstream calls, downstream calls, as well as the span count and related metric alerts on the trace analysis page.
- HTTP status code allowlist
- By default, status codes greater than or equal to 400 are classified as erroneous calls. To exclude specific status codes from being treated as errors, configure an HTTP status code allowlist based on actual needs. Once configured, allowlisted HTTP status codes are treated as successful in RED metrics and error statistics.
- Data impact: Error count metrics and span status for HTTP servers/clients.
- Functional impact: Service overview, trace analysis, span status, and more.
Data reporting
Data reporting settings include settings for reporting of metrics, logs, and traces. This option is enabled by default. You can disable or enable it as needed.
Log configuration management
The global switch for TLS access. It is enabled by default. You can disable or enable it as needed.
danger
Disabling TLS will simultaneously delete historical log data and the log topic. Deleted data cannot be recovered. Proceed with caution.
Storage settings
Data encryption settings are currently supported. To configure data encryption, click Modify settings, select an appropriate encryption method for your scenario, and then click Save.
This parameter primarily affects Server-side Monitoring trace data stored in TLS. It supports two encryption methods: Service Key (SSE-TLS) and User Key (SSE-KMS). Detailed descriptions are as follows:
danger
- Select one data encryption method that suits your actual scenario. Once the encryption method is selected, you cannot change it, but you can enable or disable it. Proceed with caution. For usage limits and configuration instructions, see Data encryption.
- If the master key is deleted or disabled, customer-managed keys will become invalid, causing read/write failures for trace data stored in TLS by Server-side Monitoring. Therefore, make sure that the keys are available and enabled.
Encryption method | Description |
Service Key (SSE-TLS) | The default encryption method provided by TLS. This method requires no additional configuration and enables a transparent encryption experience. It is suitable for scenarios that require rapid deployment of data encryption without self-managed keys (managed by the service provider) and long-term key stability. tip This encryption method is free of charge. |
User Key (SSE-KMS) | Keys generated using Key Management Service (KMS). KMS provides secure key storage, generation, encryption, and rotation. This solution offers full lifecycle control and proactive management. It is suitable for self-managed key scenarios that require security compliance, periodic permission audits, and reduced leakage risks. tip
|
Performance profiling
After you enable Continuous CPU profiling, you can collect CPU performance metrics for specified services and pods and create profiling tasks in Infrastructure Monitoring. For related operations, see Performance profiling.
warning
- Before enabling this toggle, ensure that the apmplus-opentelemetry-collector add-on in the VKE cluster where the target service resides has been upgraded to V3.2.0 and that the DaemonSet deployment has been enabled. For more information, see Upgrading the add-on and apmplus-opentelemetry-collector.
- Continuous CPU profiling incurs additional resource overhead. Enable it as needed.
- After this toggle is disabled, the system stops collecting CPU profiling data, and no new profiling tasks can be created.
Last updated: 2026.09.21 14:25:29
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
