Configuring private RUM data collection
IBM® NS1 Connect® ingests data that is collected from shared or private resources to inform how the platform distributes traffic across your application endpoints and services.
While the turnkey solution includes collecting community data from a pool of top CDNs and cloud services, users can configure RUM data collection from private resources by using one of two methods:
- Option A: Collect private data by using an embedded JavaScript tag
- Embed a JavaScript tag on your web properties to measure your private application servers, web servers, or CDNs. The JavaScript runs asynchronously in the background with each page load to collect RUM data directly from your user "eyeballs" or impressions.
- Option B: Beaconing data via gRPC or HTTP
- If you are already collecting RUM data from your endpoints, you can beacon the telemetry to the NS1 Connect platform by using the API. With this method, you bring your own (BYO) data from your CDN footprint or any combination of servers, data centers, or cloud providers. Beaconed data must contain a performance-based measurement, such as latency, to reference when routing.
Depending on your private data collection method, you create RUM-based applications and jobs corresponding to a resource, specifying the job type (JavaScript or bulk beaconing) and other configuration settings.
Before you begin
Consult with IBM support or your dedicated support engineer for guidance on the best data collection methods for your organization and to overview the configuration process. If you plan to use the JavaScript tag for implementation, IBM support can provide you with a custom JavaScript tag.
Procedure
Refer to the following instructions for the method that you want to use for configuring private data collection.