Private RUM data collection is available only to IBM NS1 Connect accounts with the RUM-based (Pulsar) traffic steering solution. Contact your dedicated sales representative or email email@example.com to learn more.
First, you must set up an asset on the resource that maps to the delivery method, endpoint, or provider you wish to measure.
The size of the asset required will depend on your specific use case. For example, if you are interested in monitoring availability and latency, measuring a small asset (e.g., 1x1-pixel image) is best. However, if you have a streaming use case and are interested in the availability and TTLB of a larger-sized asset, NS1 recommends working with an NS1 customer success engineer to determine the appropriate size for the asset (based on throughput).
When setting up your target, specify the following headers:
Ensure the asset is available via HTTP and HTTPS. Ignore query strings to bypass browser caching. Ensure the browser's CORS option can allow *.nsone.net, *.ns1.com, and *.nsone.co for the most consistent experience.
A RUM (Pulsar) application represents a group of resources or assets from which the NS1 Connect platform ingests RUM data. Each application is identifiable by its unique application ID (app ID). The NS1 Connect platform references the app ID to determine which set of jobs should take the measurement. After configuring the application, you create a RUM (Pulsar) job for each monitored resource. Each resource will host a single-pixel image to track real-time availability and performance upon each page load.
If using the API to configure RUM applications and jobs, you must associate each job with the respective application using the unique app ID.
Refer to Creating Pulsar applications and jobs for instructions.
<body> block. Note that your unique appID is automatically encoded.
After creating a RUM application and the corresponding jobs, you can connect the job directly to a DNS answer like a monitor or third-party data feed. For instructions, refer to Connecting a monitor or data source to a DNS answer.