Release Notes
Configuration Item | Description |
API filtering | Filter out unwanted APIs by API name, for example: operationName(.*?), operation(*). Multiple rules are separated by commas. |
error type filtering | The error types that are filtered will not be counted in the error analysis. Please enter the error types to be filtered according to the regular expression, and separate multiple error types with commas. |
HTTP status code filtering | The HTTP status codes that are filtered will not be counted in the error analysis. By default, HTTP status codes greater than 400 are considered errors. Please separate multiple HTTP status codes with commas. |
URL convergence | After enabling, the system will aggregate and display the same type of APIs based on the customized convergence rule regular expressions and convergence threshold. |
Convergence threshold | This parameter specifies the minimum quantity for URL convergence. For example, if the threshold is 100, convergence will be performed when the number of APIs in line with the regex reaches 100. |
Convergence rule regex | Customize URL convergence rules with regular expressions. For example, if the number of APIs whose first half is /service/demo/ exceeds 100, aggregate and display such APIs. Then the convergence threshold should be filled in as 100, and the convergence rule regular expression is /service/demo/(.*?). |
Exclusion rule regex | This parameter excludes specified URLs from convergence. For example, to exclude URLs starting with service/demo/example from convergence, the regex should be /service/demo/example/(.*?). |
Configuration Item | Description |
Probe master switch | Data reporting can be temporarily disabled through the master switch for the probe. Once disabled, the application will no longer incur APM fees, and there is no need to restart the application. If you need to permanently disable data reporting, please uninstall the probe to avoid unnecessary performance overhead. Note: This feature is only supported by probes of version 1.16-20241031 and above. |
Enable method stack snapshots | If an API call duration frequently exceeds the slow call monitoring threshold, it may automatically generate a method stack execution snapshot. You can filter out calls with method stack snapshots on the Distributed Tracing page. On the Trace details page, if a call includes a method stack snapshot, the method stack snapshot button, will be displayed; click it to view the execution details of the local method stack. Note: This feature is only supported by probes of version 1.16-20240831 and above. |
API filtering | For matched APIs, the probe will not report relevant link data. Please enter the APIs to be filtered according to the regular expression, and separate multiple APIs with commas. Note: This feature is only supported by probes of version 1.16-20240328 and above. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback