Application Real-Time Monitoring Service (ARMS) Browser Monitoring provides a variety of SDK configuration items to suit a wide range of requirements. For example, you can use these configuration items to ignore URLs, API operations, or JavaScript (JS) errors, aggregate pages by removing non-key characters from URLs, and reduce reported data or workloads by using random sampling.

Methods in this topic

pid | uid | tag | page | setUsername | enableSPA | parseHash | disableHook | ignoreUrlCase | urlHelper | apiHelper | parseResponse | ignore | disabled | sample | sendResource | useFmp | enableLinkTrace | release | environment | behavior | c1\c2\c3 | autoSendPerf

Use SDK configuration items

You can use SDK configuration items by using one of the following methods:

  • When you install a Browser Monitoring agent to a page, add parameters to config based on your requirements.

    For example, in the following sample code, aside from the default pid parameter, the enableSPA parameter for single page applications (SPAs) is added to config:

    <script>
    !(function(c,b,d,a){c[a]||(c[a]={});c[a].config={pid:"xxxxxx",enableSPA:true};
    with(b)with(body)with(insertBefore(createElement("script"),firstChild))setAttribute("crossorigin","",src=d)
    })(window,document,"https://retcode.alicdn.com/retcode/bl.js","__bl");
    </script>                    
  • After a page is initialized, call the setConfig method in the JavaScript code to modify the configuration items.

    The following table describes the parameter of the __bl.setConfig(next) method.

    Parameter Type Description Required Default value
    next Object The configuration item and its value that you want to modify. Yes None

    The following code provides an example on how to modify the disableHook parameter to disable automatic API reporting:

    __bl.setConfig({
        disableHook: true
    });            

pid

Field Job type Description Required Default
pid String The unique ID of the project. It is automatically generated by ARMS when it creates a site. Yes None

[Back to Top]

uid

Field Job type Description Required Default
uid String The ID of the user. The value is an identifier of the user and can be used to search for the user. You can specify a custom value. If you do not specify this parameter, the SDK is automatically generated and updated every six months.
  • Weex scenario: required
  • Other scenarios: not required
  • Weex Scenario: None
  • Other scenarios: automatically generated by the SDK

The following code provides an example on how to call the setConfig method to modify the SDK configuration item:

__bl.setConfig({
    uid: 12345
});        
Note You cannot call the setConfig method to modify the uid parameter when you monitor mini programs. Instead, you can call the setUsername method to identify a user.

[Back to Top]

tag

Field Job type Description Required Default
tag String The input tag. Each log carries a tag. No None

[Back to Top]

page

Field Job type Description Required Default
page String The page name. No By default, the key part of the current page URL is taken: host + pathname.
Note You can use the ignoreErrors property to query errors that you want to report. For more information, see ignore.

[Back to Top]

setUsername

Field Job type Description Required Default
setUsername Function Used to set a method that needs to return a user name of type String. No None

This configuration item is used to create a function. This function is used to obtain a username as a string. After the username is obtained, you can implement end-to-end session tracing and query sessions based on the username to troubleshoot issues.

Note If the username cannot be obtained when the page is initialized, you can set the return value to null instead of a temporary username. If you set the return value to null, the setUsername method will be called again to obtain the username when the SDK is used to send logs. However, if you set the return value to a temporary username, the temporary username is used and setUsername is not called again to obtain the actual username.

The following code provides an example on how to call the setConfig method to modify the SDK configuration item:

__bl.setConfig({
    setUsername: function () {
        return "username_xxx";
    }
});            

[Back to Top]

enableSPA

Field Job type Description Required Default
enableSPA Boolean Listen to hashchange events on the page and report the PV again. This is applicable to single-page application scenarios. No (supported only in Web scenarios) false

[Back to Top]

parseHash

Field Job type Description Required Default
parseHash Function Used with enableSPA. No See below

In an SPA, when the enableSPA parameter is set to true and the page triggers a hashchange event, the parseHash parameter is used to parse the URL hash into the page name indicated by the Page field. For more information about SPAs, see Page data reporting of SPAs.

Default value

The default value is obtained by using the following string processing method:

function (hash) {
    var page = hash ? hash.replace(/^#/, '').replace(/\?.*$/, '') : '';
    return page || '[index]';
}           

Typically, you do not need to modify this parameter. However, if you want to use a custom page name to report page-specific data, or if the URL hash is complex, you can modify this configuration item. Example:

// Define the mapping between the URL hashes and page names. 
var PAGE_MAP = {
    '/': 'Homepage',
    '/contact': 'Contact us',
    '/list': 'Data list',
    // ...
};
// Call the SDK method after the page is loaded. 
window.addEventListener('load', function (e) {
    // Call the setConfig method to modify the parseHash configuration item. 
    __bl.setConfig({
        parseHash: function (hash) {
            key = hash.replace(/\?.*$/, '');
            return PAGE_MAP[key] || 'Unknown page';
        }
    });
});

[Back to Top]

disableHook

Field Job type Description Required Default
disableHook Boolean Disable AJAX request listeners. No false: By default, it listens and is used to report the success rate of API calls.

[Back to Top]

ignoreUrlCase

Field Job type Description Required Default
ignoreUrlCase Boolean Ignore Page URL case. No true: Case insensitive by default.

[Back to Top]

urlHelper

Field Job type Description Required Default
urlHelper * Instead of the old parameter ignoreUrlPath, it is used to configure URL filtering rules. No See below

When a page URL is in the format of http://example.com/projects/123456 (where the value that follows projects is the project ID), page-specific data is reported with the page name as example.com/projects/123456. In this case, data of similar pages about projects cannot be aggregated. If you want to aggregate data of similar pages, set the urlHelper parameter to remove non-key characters from the page URLs, such as the project ID in this example.

Notice
  • The urlHelper parameter replaces the ignoreUrlPath parameter to ignore non-key characters in page URLs. If you specify the ignoreUrlPath parameter, the configuration still takes effect. If both the ignoreUrlPath and urlHelper parameters are specified, the configuration specified by the urlHelper parameter takes effect.
  • This configuration item is valid only when the page URL is automatically obtained and used as the page name for data reporting. This parameter is invalid when you manually modify the page name by calling the setPage or setConfig method, or when the enableSPA parameter is set to true. For more information about the setConfig method, see API reference.

Default value

The default value of this configuration item is the array in the following sample code. In most cases, you do not need to modify the value:

[
    // Replace all digits in the URL with asterisks (*). 
    {rule: /\/([a-z\-_]+)?\d{2,20}/g, target: '/$1**'},
    // Remove the forward slash (/) at the end of the URL. 
    /\/$/
]                    

The default value of this parameter is used to replace digits with asterisks (*) in strings such as xxxx/123456. For example, xxxx/00001 and xxxx/00002 are modified to xxxx/**.

Value types

The value of the urlHelper parameter can be of the following types:

  • String or RegExp (regular expression): The matched strings are removed.
  • Object<rule, target>: The object contains two keys, rule and target, which are the input parameters of the replace method in the JavaScript string. For more information, see the String::replace method described in related JavaScript tutorials.
  • Function: The original string is used as the input parameter for creating a function. The return value of the function is used as the page name.
  • Array: This value type is used to set multiple rules for removing non-key characters in page URLs. The value of each rule can be one of the preceding types.

[Back to Top]

apiHelper

Field Job type Description Required Default
apiHelper * Instead of the old parameter ignoreApiPath, it is used to configure API filtering rules. No See below

This parameter is used to remove non-key characters in page URLs when page-specific data about API operations is automatically reported. The usage and function of this parameter are the same as those of urlHelper.

Notice The apiHelper parameter replaces the ignoreApiPath parameter to ignore non-key characters in URLs of API operations. If you specify the ignoreApiPath parameter, the configuration still takes effect. If both the ignoreApiPath and apiHelper parameters are specified, the configuration specified by the apiHelper parameter takes effect.

Default value

The default value of this parameter is an object and does not need to be modified:

{rule: /(\w+)\/\d{2,}/g, target: '$1'}                    

The default value of this parameter is used to remove the digits in URL strings such as xxxx/123456.

If you want to report parameters after ? in the page-specific data of API operations, such as the pid parameter in https://arms.console.aliyun.com/apm?pid=fr6fbgbeot, perform the following steps to manually report the data:

  • Call the ignore method to disable automatic data reporting. For more information, see ignore.
  • Call the api() method to manually report the page-specific data about API operations. For more information, see api().

[Back to Top]

parseResponse

Field Job type Description Required Default
parseResponse Function Used to parse the data returned during the automatic reporting API. No See below

This configuration item is used to parse the data returned when the page-specific data of API operations is automatically reported.

Default value

The following sample code shows the default configurations:

function (res) {
    if (!res || typeof res !== 'object') return {};
    var code = res.code;
    var msg = res.msg || res.message || res.subMsg || res.errorMsg || res.ret || res.errorResponse || '';
    if (typeof msg === 'object') {
        code = code || msg.code;
        msg = msg.msg || msg.message || msg.info || msg.ret || JSON.stringify(msg);
    }
    return {msg: msg, code: code, success: true};
}                    

The preceding code is used to parse the returned data and extract the msg and code parameters. Typically, you do not need to modify the default configurations. You can also modify the configurations based on your business requirements.

[Back to Top]

ignore

Field Job type Description Required Default
ignore Object Ignore the specified URL/API/JS error. Logs that meet the rules will be ignored and will not be reported. They include sub-configuration items ignoreUrls, ignoreApis, ignoreErrors, and ignoreResErrors. No See below

The value of the ignore parameter is an object that contains four properties: ignoreUrls, ignoreApis, ignoreErrors, and ignoreResErrors. You can set one or more properties of the parameter value.

Default value

The following sample code shows the default configurations:

ignore: {
        ignoreUrls: [],
        ignoreApis: [],
        ignoreErrors: [],
        ignoreResErrors: []
    },                    

ignoreUrls

The ignoreUrls property is used to ignore URLs that comply with the rule you specified. Logs from these URLs are not reported. The value of this property can be a string (indicated by the String type), a regular expression (indicated by the RegExp type), a method (indicated by the Function type), or an array that contains data of the preceding types. Example:

__bl.setConfig({
                ignore: {
                    ignoreUrls: [
                    'http://host1/',  // Specify a string.
                    /.+?host2.+/,     // Specify a regular expression.
                    function(str) {   // Specify a method.
                        if (str && str.indexOf('host3') >= 0) {
                            return true; // The data is not reported.
                        }
                        return false; // The data is reported.
                    }]
                }
            });                    

ignoreApis

The ignoreApis property is used to ignore APIs that comply with the rule you specified. The value of this property can be a string (indicated by the String type), a regular expression (indicated by the RegExp type), a method (indicated by the Function type), or an array that contains data of the preceding types. Example:

__bl.setConfig({
                ignore: {
                    ignoreApis: [
                    'api1','api2','api3', // Specify a string.
                    /^random/,  // Specify a regular expression.
                    function(str) { // Specify a method.
                        if (str && str.indexOf('api3') >= 0) return true; // The data is not reported.
                        return false; // The data is reported.
                    }]
                }
            });                    

ignoreErrors

The ignoreErrors property is used to ignore JS errors that comply with the rule you specified. The value of this property can be a string (indicated by the String type), a regular expression (indicated by the RegExp type), a method (indicated by the Function type), or an array that contains data of the preceding types. Example:

__bl.setConfig({
                ignore: {
                    ignoreErrors: [
                    'test error', // Specify a string.
                    /^Script error\.?$/, // Specify a regular expression.
                    function(str) { // Specify a method.
                        if (str && str.indexOf('Unknown error') >= 0) return true;   // The data is not reported.
                        return false; // The data is reported.
                    }]
                }
            });            

ignoreResErrors

The ignoreResErrors property is used to ignore resource errors that comply with the rule you specified. The value of this property can be a string (indicated by the String type), a regular expression (indicated by the RegExp type), a method (indicated by the Function type), or an array that contains data of the preceding types. Example:

__bl.setConfig({
                ignore: {
                    ignoreResErrors: [
                    'http://xx/picture.jpg', // Specify a string.
                    /jpg$/, // Specify a regular expression.
                    function(str) { // Specify a method.
                        if (str && str.indexOf('xx.jpg') >= 0) return true;   // The data is not reported.
                        return false; // The data is reported.
                    }]
                }
            });

[Back to Top]

disabled

Field Job type Description Required Default
disabled Boolean Specifies whether to disable the log reporting function. No false

[Back to Top]

sample

Field Job type Description Required Default
sample Integer The log sampling configuration. The value is an integer from 1 to 100. The performance logs and success API logs are sampled at the 1/sample ratio. For more information about the metrics of performance logs and success API logs, see Statistical metrics. No 1

Benefits:

  • Reduces costs by reporting only sampled API data. We recommend that you identify the data that does not require monitoring by setting the ignore parameter. For more information, see ignore.
  • Reduces the performance overhead of data collection.

Description:

  • You can set this configuration item to randomly select and report performance logs and logs about successful API operations. This reduces the volume of reported data and the workloads. When ARMS processes the reported logs in the background, ARMS restores the data based on the sampling configurations. In this way, metrics such as the JS error rate or API failure rate are not affected by sampling and remain accurate. However, when you set this parameter, you may be unable to obtain the detailed data such as the API details.

  • The default value of the sample parameter is 1. The valid values of this parameter are integers from 1 to 100. The sampling rate can be calculated by using the following formula: 1/Value of sample. For example, the parameter values 1, 10, and 100 indicate the sampling rates of 100%, 10%, and 1%.

Warning When the total data volume is small and random sampling is still performed, a large deviation may be introduced to the statistical result. We recommend that you use this configuration item for the websites whose daily average page views (PVs) is more than 1 million.

[Back to Top]

sendResource

Field Job type Description Required Default
sendResource Boolean Reports static resources on the page. No false

If the sendResource parameter is set to true, the static resources loaded to the current page are reported when the load event is triggered for the page. If the page loading is slow, you can view the waterfall chart of static resources on the Session Traces page to determine the cause.

The following code provides an example on how to set the sendResource parameter:

<script>
!(function(c,b,d,a){c[a]||(c[a]={});c[a].config={pid:"xxxxxx",sendResource:true};
with(b)with(body)with(insertBefore(createElement("script"),firstChild))setAttribute("crossorigin","",src=d)
})(window,document,"https://retcode.alicdn.com/retcode/bl.js","__bl");
</script>            
Note When you want to troubleshoot slow page loading, you must configure the sendResource parameter in config, as shown in the preceding sample code. This way, the static resources are reported when the load event is triggered. If you call the setConfig method, the static resources may be reported after the load event is complete. In this case, the sendResource parameter cannot help you identify the cause of slow page loading.

[Back to Top]

useFmp

Field Job type Description Required Default
useFmp Boolean Collects first-screen FMP(First Meaningful Paint, first valid rendering) data. No false

[Back to Top]

enableLinkTrace

Field Job type Description Required Default
enableLinkTrace Boolean For more information about back-to-back Tracing Analysis, see Use the front-to-back tracing feature to diagnose API errors. No (only supported by Web scenarios, Alipay applets, WeChat applets, and DingTalk applets) false

[Back to Top]

release

Notice You must configure release in config during page initialization. Do not call the setConfig method.
Field Job type Description Required Default
release String The version of the application. We recommend that you configure this parameter to view the report information of different versions. No undefined

[Back to Top]

environment

Field Job type Description Required Default
environment String The environment field. Valid values: prod, gray, pre, daily, and local.
  • The value prod indicates an online environment.
  • The value gray indicates a phased-release environment.
  • The value pre indicates a staging environment.
  • The value daily indicates a daily environment.
  • The value local indicates a local environment.
No prod

[Back to Top]

behavior

Field Job type Description Required Default
behavior Boolean Specifies whether to record the user behavior that reports errors for easy troubleshooting. No (supported only in Web and mini-program scenarios) The default value of Browser is true, and the default value of mini program is false.

[Back to Top]

autoSendPerf

Field Job type Description Required Default
autoSendPerf Boolean Specifies whether to allow automatic sending of performance logs. No true

[Back to Top]

c1\c2\c3

In addition to the preceding configuration items, the ARMS SDK provides three custom configuration items that you can configure fields to meet your business requirements. After you configure the fields, the fields values are included in all reported logs.

Field Job type Description Required Default
c1 String Custom service field. Each log carries the field. No None
c2 String Custom service field. Each log carries the field. No None
c3 String Custom service field. Each log carries the field. No None
Note c1\c2\c3 is the data that is carried in all reports on the current custom page. Generally, c1\c2\c3 is related to your services. When you initialize Browser Monitoring SDK for JavaScript, you can specify SDK parameters to query data, such as the VIP level of a user.

[Back to Top]