The Platforms page is where the customer specifies the CDNs, clouds, data centers or other end-points that should be monitored and used with Openmix. A platform should be setup for each routing end-point on which you would like to report. Most often a platform represents a CDN, cloud region or individual instance, if using Openmix for GSLB.
On clicking this menu item, the customer will be presented with the following screen.
This screen shows a full list of all the platforms configured for either reporting, radar measurements or the Sonar and Fusion services.
The table shows:
|Name||The user-defined name of the platform.|
|ID||The ID generated for the for the platform, useful for API access and reporting.|
|Openmix Alias||The alias with which to refer to the platform from Openmix applications.|
|Apps||The number of Openmix applications using the platform.|
|Radar||Whether the platform is setup to use community or private Radar measurements.|
|Sonar||Whether Sonar is activated on this platform.|
|Fusion||Whether Fusion is activated on this platform.|
Creating a Platform
To add a platform, click the ’+’ button at the top of the Platforms page.
Editing a Platform
Editing a platform is as easy as clicking on the platform row in the table and clicking the Edit button.
Once you have changed the configuration, simply click Save, as you would with a new application and this will bring you back to the platforms screen with your changes saved.
Once you have clicked Add Platforms you will see the following page where you will configure the Platform you are going to monitor. In this section you will provide names for the platform that will be used to display information and used within the other services that Citrix supplies such as Openmix.
Under the Simple settings enter/select the following information:
|Category||The type of service the platform represents.Platforms are handled differently in Radar and Openmix, depending on the type.|
|Platform||Select the Platform you wish to test, for example Akamai, BitGravity, Amazon, Azure, etc.|
|Report Name||Name for the platform used in display and reporting.|
|Openmix Alias||The alias that Openmix applications will use to identify the platform.|
|Tags||Tags can be assigned to platforms so they can organized as needed.|
When you select an existing platform the Report Name and Openmix Alias fields will be filled in.You can leave these fields with the default values or modify them as you prefer.
Click Next to continue to the optional configuration. When finished with the optional configuration, click Complete to add the platform.
Radar Probes Settings
Radar probes can be specified for each platform. In most cases this is only necessary if you are setting up a private platform for Radar monitoring. Public platforms provide data gathered by the community and can be relied on for most uses.
There is a probe for each type of data collected, such as: HTTPS Response Time, HTTP Throughput, HTTPS Cold Start (for availability), etc. Most Radar setups have probes for at least Cold Start and Response Time, with Throughput in some cases.
Each probe has the following settings:
|Probe Type||The value for which the data should be reported.There are separate probes for each protocol (HTTP/HTTPS) and the type of data that will be collected (Cold Start, Round Trip Time, Throughput, etc.).|
|URL||The URL to the probe object.|
|Object Type||The type of file that is used to take the measurement. In most cases you will want to download the “Timing Object” from the link in the dialog and choose “Image File”. For probes of DSA services, you will normally choose “Web Page (Dynamic)”.|
Click Add Probe in the lower left of the dialog and add information for each probe. Click Save after all the probes have been entered.
Advanced Radar Settings
You can control the behavior of the Radar checks for the platform.These should only be changed if you understand the impact on your Openmix application.
The following options are available:
|Platform Weight||Radar uses a weighting system to help customers prioritize their custom tests, the higher the number the higher priority of this private test.Typically, this is used when you have a number of custom tests, if you are configuring only one leave it as the default.||10, no weighting|
|Weighted Countries||You can override the Platform Weight for certain countries by inputting the desired countries.The country is specified using the ISO country codes.||0, no weighting|
|Country Weight||If Weighted Countries are specified, this weight will be applied to the countries and will override the Platform Weight.|
|Cache Busting||Disabling this setting can cause some of the measurements to be optimistic due to cached versions of the test object being reported.||Enabled|
Sonar is a live-ness check service that can be used to monitor web-based services for availability.Sonar works by making HTTP or HTTPS requests from multiple points-of-presence around the world to a URL that you specify.
Sonar is enabled in the platform configuration.Please refer to the Sonar user guide for more information.