The use of CDN attribution in Kentik Detect is covered in the following topics:
Note: To use CDN attribution at least one of your DNS servers must be running Kentik’s kprobe host agent software (see Host Configuration).
Background information about CDN attribution is covered in the following topics:
|top | section|
CDN attribution makes it possible for Kentik Detect to determine whether a given flow record originated or terminated with a commercial CDN, and to store that information for each record using the following two columns of the Kentik Data Engine (KDE):
Once stored in KDE (see KDE Tables), the columns can be used for both group-by dimensions and filters in Kentik Detect queries (e.g. in Data Explorer, Dashboards, etc.) as described in Applying CDN Attribution.
|top | section|
While fairly simple in theory, mapping IPs to CDNs is non-trivial in practice, mainly because CDNs rely on two infrastructure scenarios:
The above infrastructure scenarios may be blended in varying degrees by different types of CDNs, e.g. commercial, multi-tenant CDNs as distinct from single-purpose CDNs. But the dynamic algorithms employed by Kentik for CDN attribution allow IP mapping across the spectrum:
The following diagram provides a simplified visual description of how CDN attribution operates:
Kentik has designed CDN attribution as a self-learning system that updates itself once a day. The system constantly discovers new CDNs as they are born and new IPs (caching servers) as they are deployed.
Preparing your Kentik setup for CDN attribution involves the following tasks:
To configure CDN attribution in the portal:
Note: DNS servers covering different geographical zones will typically result in distinct (largely non-overlapping) IP-to-CDN mappings. To export the best IP-to-CDN mapping data to KDE, Kentik recommends that CDN attribution users deploy kprobe on as many of their DNS servers as possible. This approach has the added advantage of providing highly granular NPM metrics for those devices (see Host Metrics and Dimensions).
Once you’ve registered one or more DNS servers with Kentik and configured them for CDN attribution, the flow records stored for those devices in KDE (see KDE Tables) will include CDN Attribution Dimensions. You will now be able to use those dimensions in Kentik Detect queries:
Using CDN for filters or group-by dimensions in Data Explorer or Dashboard queries can reveal (among other things) how much of your traffic is coming from (shown in screenshot below) or going to various CDNs.
In this article: