Download full document:

Citrix Monitor Service API 1808

The Monitor Service API is built on the SQL Server Monitor database that is populated during processing and consolidation. The Monitor Service API is based on the ASP.NET Web API Framework.

The Monitor Service API uses the Open Data (OData) protocol, which is a Web protocol for querying and updating data, built upon Web technologies such as HTTP.

The Monitor Service API is a REST-based API that can be accessed using an OData consumer. OData consumers are applications that consume data exposed using the OData protocol. ASP.NET Web API Framework supports OData Version 3 and Version 4. You can use either endpoints to run your queries.

You can use the API to:

  • Analyze historical trends for future planning

  • Perform detailed troubleshooting of connection and machine failures

  • Extract information for feeding into other tools and processes; for example, using Microsoft Excel's PowerPivot tables to display the data in different ways

  • Build a custom user interface on top of the data that the API provides

  • Run aggregation queries with the OData Version 4 endpoints to get basic grouping and aggregation functionality.

Data Available using the API

The following types of data are available through the Monitor Service API:

  • Data relating to connection failures

  • Machines in a failure state

  • Session usage

  • Logon duration

  • Load balancing data

  • Hotfixes applied to a machine

  • Hosted application usage

  • Machine level CPU, Memory and Disk usage

  • Process level CPU and memory usage

  • Application usage and failure data

Monitor Service Schema

For the details of the Monitor Service schema, please refer to: Monitor Service Schema

To determine the values returned by the Monitor Service OData API, see: Citrix Monitor Data Model

How to Access the Monitor Service Data

Citrix recommends that you don't use the Methods endpoints of the Monitor Service API directly. They contain operations used by Director to retrieve data requiring complex grouping and high performance standards. The results are available on the Dashboard and Trends pages, and in the export reports in Director.

Data Access Privilege

To use the Monitor Service OData API, you must be a XenApp and XenDesktop administrator. To call the API, you require read-only privileges; however, the data returned is determined by XenApp and XenDesktop administrator roles and permissions.

For example, Delivery Group Administrators can call the Monitor Service API but the data they can obtain is controlled by Delivery Group access set up using Citrix Studio.

For more information about XenApp and XenDesktop administrator roles and permissions, see Delegated Administration.

Data Access Security

If you choose to use TLS, you must configure TLS on all Delivery Controllers in the Site; you cannot use a mixture of TLS and non-TLS. To improve the security of the Citrix Virtual Apps and Desktops service, Citrix will block any communication over Transport Layer Security (TLS) 1.0 and 1.1 as of March 15, 2019, allowing only TLS 1.2 communications.

To enforce the usage of TLS 1.2, update the registry as described in the Knowledge Center article CTX245765

To secure Monitor Service endpoints using TLS, you must perform the following configuration. Some steps need to be done only once per Site, others must be run from every machine hosting the Monitor Service in the Site. The steps are described below.

Part 1: Certificate registration with the system

  1. Create a certificate using a trusted certificate manager. The certificate must be associated with the port on the machine that you wish to use for OData TLS.
  2. Configure the Monitor Service to use this port for TLS communication. The steps depend on your environment and how this works with certificates. The following example shows how to configure port 443:
  3. Associate the certificate with a port:
netsh http add sslcert ipport=


Tip: In a PowerShell command window, ensure you put single quotes around the GUID in the appID, as shown above, or the command will not work. Note that a line break has been added to this example for readability only.

Part 2: Modify the Monitor Service configuration settings

  1. From any Delivery Controller in the Site, run the following PowerShell commands once. This removes the Monitor Service registration with the Configuration Service.
    asnp citrix.\* \$serviceGroup = get-configregisteredserviceinstance -servicetype Monitor | Select -First 1 ServiceGroupUid remove-configserviceGroup -ServiceGroupUid \$serviceGroup.ServiceGroupUid
  2. Do the following on all Controllers in the Site:
    • Using a cmd prompt, locate the installed Citrix Monitor directory (typically in C:\Program Files\Citrix\Monitor\Service). Within that directory run: Citrix.Monitor.Exe -CONFIGUREFIREWALL -ODataPort 449 -RequireODataSsl
    • Run the following PowerShell commands: asnp citrix.\* (if not already run within this window) get-MonitorServiceInstance | register-ConfigServiceInstance Get-ConfigRegisteredServiceInstance -ServiceType Config | Reset-MonitorServiceGroupMembership

Data Access Protocol

The Monitor Service API is a REST-based API that can be accessed using an OData consumer. OData consumers are applications that consume data exposed using the OData protocol. OData consumers vary in sophistication from simple web browsers to custom applications that can take advantage of all the features of the OData Protocol.

Every part of the Monitor Service data model is accessible and can be filtered on the URL. OData provides a query language in the URL format you can use to retrieve entries from a service. You can use the OData V3 or OData V4 endpoints to run your queries. OData V4 supports aggregation queries.

The query is processed on the server side and can be filtered further using the OData protocol on the client side.

The data modeled falls into three categories: aggregate data (the summary tables), current state of objects (machines, sessions, etc.), and log data, which is really historical events (connections, for example).

Note: Enums are not supported in the OData protocol; integers are used in their place. To determine the values returned by the Monitor Service OData API, see Monitor Service Data Model.

What is OData Protocol?

OData (Open Data Protocol) is an OASIS standard that defines a set of best practices for building and consuming RESTful APIs. OData helps you focus on your business logic while building RESTful APIs without having to worry about the various approaches to define request and response headers, status codes, HTTP methods, URL conventions, media types, payload formats, query options, etc.

OData also provides guidance for tracking changes, defining functions/actions for reusable procedures, and sending asynchronous/batch requests.

OData RESTful APIs are easy to consume. The OData metadata, a machine-readable description of the data model of the APIs, enables the creation of powerful generic client proxies and tools.

OData Consumers:

Client Libraries:

Basic Tutorial:

As OData Provider, Citrix Monitor Service API is implemented by ASP.NET Web API.

For more detail about using ASP.NET Web API to create OData V4 endpoints, see OData v4 Web API

Access methods

The following examples show how to export Monitor Service data using the OData API. This topic also provides a list of URLs for available data sets.

Access using Raw XML

  1. Place the URL for each data set into a web browser that is running with the appropriate administrative permissions for the XenApp and XenDesktop Site. Citrix recommends using the Chrome browser with the Advanced Rest Client add-in.

  2. View the source.

Access using PowerPivot with Excel

  1. Install Microsoft Excel.

  2. Follow the instructions here to install PowerPivot (depending on whether or not you are using 2010 or 2013):

  3. Open Excel (running with the appropriate administrative permissions for the XenApp and XenDesktop Site).

Access using Excel 2010

  1. Click the PowerPivot tab.

  2. Click PowerPivot Window.

  3. Click From Data Feeds in the ribbon.

  4. Choose a Friendly Connection Name (for example: XenDesktop Monitoring Data) and enter the data feed url: http://{dc-host}/Citrix/Monitor/OData/v4/Data (or https: if you are using SSL).

  5. Click Next.

  6. Select the tables you want to import into Excel and click Finish. The data is retrieved.

Access using Excel 2013

  1. Click the Data tab.

  2. Choose From Other Sources > From OData Data Feed

  3. Enter the data feed url: http://{dc-host}/Citrix/Monitor/OData/v4/Data (or https: if you are using SSL) and click Next .

  4. Select the tables you want to import into Excel and click Next.

  5. Accept name defaults or customize names and click Finish.

  6. Choose Connection Only or Pivot Report. The data is retrieved.

You can now use PowerPivot to view and analyze the data with PivotTables and PivotCharts. For more information, see the Learning Center:

Access using LinqPad

  1. Download and install the latest version of LinqPad from

  2. Run LinqPad with the appropriate administrative permissions for the XenApp and XenDesktop Site.

    Tip: the easiest way is to download, install and run on the Delivery Controller.

  3. Click the Add connection link.

    1. To use the OData v3 endpoint, choose WCF Data Services 5.1 (OData 3) and click Next .

    2. To use the OData v4 endpoint the first time, click View More Drivers, choose the OData V4 Driver, click the Download and Enable driver link. This adds the Odata 4 driver to the list of available drivers. Subsequently, you can select OData 4 and click Next.

  4. Enter the data feed URL: http://{dc-host}/Citrix/Monitor/OData/v4/Data (or https: if you are using SSL). If necessary, enter the username and password to access the Delivery Controller. Click OK.

  5. You can now run LINQ queries against the data feed and export the data as needed. For example, right-click Catalogs and choose Catalogs.Take(100). This returns the first 100 Catalogs in the database. Choose Export>Export to Excel with formatting.

Access using Client Library

Currently Citrix Monitor Service supports OData protocol V3 and V4. So, when implement the OData consumers with various programming platforms, please select correct client libraries.

Access using C#/.NET

Calling an OData Service From a .NET Client (C#)

Code Fragment:

    /* GET http://{dc-host}/Citrix/Monitor/Odata/v4/Data/Catalogs */
    private static string ListAllCatalgs(MonitorService.DatabaseContext context)
    StringBuilder sb = new StringBuilder();
    Foreach (var c in context.Catalogs)
    return sb.ToString();
    /* GET http://Url/Machines()?$select=Name, IPAddress */
    private static void ListMachineNames(MonitorService.DatabaseContext context)
        var machines = from m in context.Machines select new { Name = m.Name, IP = m.IPAddress };
        foreach (var m in machines)
            if (m.Name != null && m.IP != null)
                Console.WriteLine("{0} : {1}", m.Name, m.IP);
    /* use the LINQ Skip and Take methods to skips the first 40 results and takes the next 10 */
    /* GET http://{dc-host}/Citrix/Monitor/Odata/v4/Machines()?$orderby=Id desc&$skip=40&$top=10 */
    private static void ListMachinesPaged(MonitorService.DatabaseContext context)
        var machines =
            (from m in context.Machines
             orderby m.Id descending
             select m).Skip(40).Take(10);

        foreach (var m in machines)
            Console.WriteLine("{0}, {1}", m.Name, m.IPAddress);
    /* GET http://Url/Catalogs()?$filter=Name eq '$Name'*/
    private static void ListCatalogByName(MonitorService.DatabaseContext context, string name)
        var catalog = context.Catalogs.Where(c => c.Name == name).SingleOrDefault();
        if (catalog != null)

Access using Java

Calling an OData Service from a Java Client based on Odata4j v0.3 library:

Code Fragment:

// create consumer instance
String serviceUrl = "http://{dc-host}/Citrix/Monitor/Odata/v4/Data/";
ODataConsumer consumer = ODataConsumer.create(serviceUrl);
// ================General Query================================
Enumerable<String> qEntitySets = consumer.getEntitySets();

Enumerable<OEntity> qList = consumer.getEntities(qEntitySets.first()).execute();

OEntity qEntity = qList.first();

OProperty<?> qProperty = qEntity.getProperties().get(0);
// =================Filter Query===========================================
/* GET http://{dc-host}/Citrix/Monitor/Odata/v4/Data/Machines */
String entitySetName = "Machines";
qList = consumer.getEntities(entitySetName).execute();

/* GET http://{dc-host}/Citrix/Monitor/Odata/v4/Data/Machines()?$select=Name, IPAddress */
qList = consumer.getEntities(entitySetName).select("Name,IPAddress").execute();

/* GET http://{dc-host}/Citrix/Monitor/Odata/v4/Machines()?$orderby=Id desc&$skip=40&$top=10 */
qList = consumer.getEntities(entitySetName).orderBy("Id desc").skip(2).top(10).execute();

/* GET http://{dc-host}/Citrix/Monitor/Odata/v4/Machines()?$filter=Name eq '$Name'*/
qList = consumer.getEntities(entitySetName).filter("Name eq 'DOMAIN\\HOSTNAME'").execute();


URLs for Available Data Sets

URL Description
http://{dc-host}/Citrix/Monitor/OData/v4/Data/Catalogs Catalog images in the Site
http://{dc-host}/Citrix/Monitor/OData/v4/Data/ConnectionFailureCategories Grouping for connection failure types
http://{dc-host}/Citrix/Monitor/OData/v4/Data/ConnectionFailureLogs Log of each connection failure in the Site
http://{dc-host}/Citrix/Monitor/OData/v4/Data/Connections Represents an initial connection or reconnect for a session
http://{dc-host}/Citrix/Monitor/OData/v4/Data/DesktopGroups Delivery Groups in the Site
http://{dc-host}/Citrix/Monitor/OData/v4/Data/FailureLogSummaries Failures (connection/machine) counts by time period and Delivery Group
http://{dc-host}/Citrix/Monitor/OData/v4/Data/Hypervisors Hosts (hypervisors) in the Site
http://{dc-host}/Citrix/Monitor/OData/v4/Data/LoadIndexes Load Index data received from the Virtual Delivery Agent (VDA)
http://{dc-host}/Citrix/Monitor/OData/v4/Data/LoadIndexSummaries Load Index averages by time period and machine
http://{dc-host}/Citrix/Monitor/OData/v4/Data/MachineFailureLogs Log of each machine failure by start and end date in the Site
http://{dc-host}/Citrix/Monitor/OData/v4/Data/Machines Machines in the Site
http://{dc-host}/Citrix/Monitor/OData/v4/Data/SessionActivitySummaries Session counts and logon data by time period and delivery group
http://{dc-host}/Citrix/Monitor/OData/v4/Data/Sessions Represents a user connected to a desktop
http://{dc-host}/Citrix/Monitor/OData/v4/Data/TaskLogs Log of all tasks and their status that have been run as part of the internal Monitor Service
http://{dc-host}/Citrix/Monitor/OData/v4/Data/Users Users that have launched a session in the Site
http://{dc-host}/Citrix/Monitor/OData/v4/Data/ProbeRules Application probes configured in the Site
http://{dc-host}/Citrix/Monitor/OData/v4/Data/ProbeEndpoints Machines running Citrix Probe Agent to probe applications in the Site
http://{dc-host}/Citrix/Monitor/OData/v4/Data/ProbeLogs Results of probes run per application
http://{dc-host}/Citrix/Monitor/OData/v4/Data/ProbeResults Results of probes run (with failure stage) per application
http://{dc-host}/Citrix/monitor/odata/v4/data/LogOnMetrics Timestamps related to Interactive Session breakdown