In addition to Radar and Sonar data, Openmix can use third party data in its decision criteria. For example, you can integrate an existing synthetic monitoring service you already use. Or you can make cost-based decisions using up-to-date usage data from your CDN provider.
Fusion Data Feeds can be accessed from the navigation menu, under the Openmix header.
For example, some common Fusion data feeds that work with Openmix applications:
- Server Availability – Ingests data from 3rd party providers like CatchPoint, Rigor and Pingdom to determine the reachability of a specific host or application.
- Server Monitoring – Metrics from providers like Rackspace and New Relic, allow Openmix to consider server run time metrics such as memory usage, CPU consumption, free disk space and network latency in the routing decision. Openmix can use the metrics to make on/off routing decisions or to make graduated routing changes by shedding traffic from a loaded server.
- CDN Cost Control - Ingests Bandwidth and Usage statistics from all the major CDNs and makes this data available real-time to Openmix applications to impact routing decisions.
- Customer defined custom data feeds - Any data at an endpoint you provide can be ingested and made available to a custom Openmix application for use in the routing decision.
|Akamai||CDN Bandwidth, CDN Usage|
|AWS CloudFront||CDN Usage|
|AWS CloudWatch||Instance Metrics|
|AWS S3||Custom Data Feed|
|CDNetworks||CDN Bandwidth, CDN Usage|
|Citrix NetScaler||Custom Data Feed|
|Edgecast||CDN Bandwidth, CDN Usage|
|Fusion Direct||Custom Data Feed|
|HTTP GET||Custom Data Feed|
|HTTP GET with Availability||Custom Data Feed|
|JSON||Custom Data Feed|
|Level3||CDN Bandwidth, CDN Usage|
|MaxCDN||CDN Bandwidth, CDN Usage|
|New Relic Apdex||Application Score|
|New Relic Server Monitoring||Instance Metrics|
|NGINX||Load Balancer Metrics|
|NGINX+||Load Balancer Metrics|
|SFR||CDN Bandwidth, CDN Usage|
|TCP Ping||Web Monitor|
The following screen shows all of the configured Fusion data feeds.The list provides an overview of the data feeds and current status.
The columns provide the following information:
|Status||The current status of data feed.The status will show either: + green – the data feed is successfully retrieving data from the service + yellow – the data feed is waiting for data to be retrieved from the service + red – the data feed cannot be retrieved from the service|
|Data Feed Name||The name given to the data feed.Optional, will default to “Service - Platform Name” if not specified.|
|Service||The name of the service being used by the data feed.|
|ID||The ID of the data feed.This is needed for accessing Fusion via the API.|
|Platform Name||The name of the Platform associated with the data feed.|
|Run Every||How often the data feed is updated from the service.|
Creating Data Feeds
If no Fusion data feeds are configured, a welcome screen will prompt you to create a new data feed.
Click the ‘Get Started’ button or ’+’ to setup a new data feed.
New Data Feeds
Click the icon of the service you would like to integrate and fill out the required configuration fields.
Each service requires different configuration parameters.You will need a username and password or a generated token for authentication and any additional service-specific configuration.
All Fusion data feeds are associated with a platform that was previously created in the Citrix Intelligent Traffic Management portal.This allows the Openmix application to query the external Fusion data for each platform and, based on the routing logic, determine if the platform should be considered available for a routing decision.
Most feeds will need to configure the following values:
|Run Every||How often the data feed is updated from the external service.Fusion will call the service at the interval specified and update the Openmix applications based on the new data.|
|Platform||The platform for which the Fusion data should be associated in the Openmix application.|
Editing Data Feeds
Editing a Fusion data feed is as easy as clicking on the data feed in the table and clicking the Edit button.
Once you have changed the configuration, click Save.This will bring you back to the data feed list with your changes saved and applied to the data feed.
Data Feed History
Fusion collects the last 100 responses from each time it is run in the data feed history.You can view the data feed status, information about the data and the payload returned from the service.After selecting the specific data feed in the list, click on the Log History button to show the history for the data feed.
To change the date selected, you can click the ’<’ or ’>’ buttons to move backwards or forwards from the current selected date or choose a specific date from from the drop down menu.Select the timestamp of the specific instance and the data returned from the service will be displayed.