Application Real-Time Monitoring Service (ARMS) captures built-in trace data, but these parameters are not tied to your business logic. For example, if you run an e-commerce application and need to find all traces associated with a specific product brand or account ID, the built-in parameters cannot help. Custom parameter extraction rules solve this problem. After you create a rule, ARMS extracts the specified values from HTTP requests and attaches them to every matching trace. You can then filter traces on the trace query page by these custom parameters.
Create an extraction rule
-
Log on to the EDAS consoleEDAS console.
In the left-side navigation pane, choose Application Management > Applications. In the top navigation bar, select a region, select a microservices namespace from the Microservices Namespace drop-down list, select Kubernetes Cluster from the Cluster Type drop-down list, and then click the name of the desired application.
In the top navigation bar, select a region. In the upper part of the page, select a microservice namespace.
From the Cluster Type drop-down list, select Kubernetes Cluster. Find the target application and click its name in the Application Name column.
In the left-side navigation pane, choose Application Settings > Application Settings.
Click the Custom parameters tab, then click Add custom parameter in the upper-right corner.
In the Add custom parameter dialog box, configure the following settings and click OK.
Parameter Description Rule name A name for the extraction rule. Interface type The API protocol type. Only HTTP is supported. Parameter extraction rules One or more conditions that define what to extract from HTTP requests. Select a source type from the drop-down list -- Parameter, Cookie, Method, or Header -- and enter the key name. Add multiple conditions to a single rule to extract several values at once. Applicable interface (Advanced setting) The API paths to which the rule applies. The default value /**(pattern matching) applies the rule to all APIs. Set this parameter based on your business requirements.Call chain full collection (Advanced setting) When turned on, ARMS collects all traces for matching requests and ignores the sample rate. Off by default. 
Example
Suppose your application receives requests like the following, and you want to search traces by the brand query parameter and the account header:
curl "http://{domain}/api/buy?brand=SIEMENS" -H "account: 123456"Add two conditions in a single rule:
Select Parameter from the drop-down list and enter
brand.Select Header from the drop-down list and enter
account.
Usage notes
Each extraction rule supports multiple conditions. Combine related conditions in a single rule to keep your configuration organized.
The Applicable interface field uses pattern matching. Use
/**to match all paths.