Managing Your Configurations
|Name||An arbitrary name that you can apply to your swarm|
|Matching Policy||Determines how a tracker will match peers to clusters. There are three policies available:
Random maps peers randomly without a specific scheme. Although it seems counter-intuitive, this policy works very good for 10.000+ concurrent users
Geo /ISP clusters peers based on network topological information and geoinformation.
ECDN / Intranet maps peers based on their public IPs and/or a given set of subnet masks.
|Web Media Selector||The Flink OTT Client SDK can track business-relevant data like traffic consumption without any further specification of a video player or similar. However, you can specify a CSS selector that points to your HTML5 player's video tag to collect even more data like buffering events, video quality and much more.|
|Allowed Domain Pattern||A Glob Pattern that specifies a domain pattern for the stream resources that your swarm should optimize. For example, if your CDN has multiple edge server domains edge01.yourcompany.yourcdn.com, edge02.youcompany, etc. In this case, you would set your allowed domain pattern to edge??.yourcompany.yourcdn.com.|
|Fetch Header||As explained in the Flink OTT Architecture Overview 🔗, trackers need to access the stream resource you want to optimize. This means the tracker has to be allowed access to the content just like a regular user. To whitelist the tracker's HTTP requests, you can white-label the