Forum Discussion

Gjon's avatar
4 years ago

Citrix Cloud Monitoring

Installation

  1. 1. Install the package from LM Exchange "Citrix Cloud"
  2. 2. Install Cloud Connector property source: Locator JYW9D7

Configuration

This datasource requires several properties to be set:

  1. CITRIX.CLOUD.CUSTOMER
      - This is found in the Citrix Cloud Portal: Identity and Access Management > API Access > Secure Clients. Copy the bolded customer ID on the page.
  2. CITRIX.CLOUD.ID
  3.   - Create a secure client, you can name it "LogicMonitor". The ID here will be used for this property.
    CITRIX.CLOUD.PASS
  4.   - This is the secret when you created the secure client.
    CITRIXCLOUD.OAUTH.KEY
  5.   - This will be autogenerated and populated by LogicMonitor using the above credentials. There is a Citrix Cloud OAuth datasource that will generate a bearer token and save it as a property on the device.
    LM.API.ID
  6.   - Create an API token in LogicMonitor with administrator privileges, copy the Access ID.
    LM.API.KEY
  7.   - This is the API token access key that was created above.
    LM.API.ACCOUNT
  8.   - This is your LogicMonitor account name, you can probably copy the subdomain of your LM portal. https://yourco.logicmonitor.com

1. Set the properties above (except CITRIXCLOUD.OAUTH.KEY) wherever you'd like depending on your folder structure. I like to set the LM API properties at the root and the Citrix Cloud properties per client (folder).
2. Find your cloud connector device in LM and add the category "PrimaryCC". Make sure you have the Cloud Connector property source installed as well!
3. The OAuth datasource should run, generating a token that the other datasources will use to query Citrix Cloud's API. You can also do a manual "poll now" to speed up the process. You should now see the CITRIXCLOUD.OAUTH.KEY property on the device.

If you have any issues, feel free to private message me!

  • Anonymous's avatar
    Anonymous

    Cool. The CSM will help direct questions to product management who can give insight into how Citrix monitoring is being planned/changed.

  • 22 minutes ago, Stuart Weenig said:

    Complete speculation here, but Citrix may be one of the new SaaS monitored apps. SaaS monitored apps can be monitored via the cloud collector instead of running from an on-prem collector in your environment. Go to the exchange and look for the "Cloud Integrations" tab. If you don't have it, reach out to your CSM.


    Thanks! I have access to the Cloud Integrations tab but don't see Citrix as an option. I will reach out to my CSM.

  • Anonymous's avatar
    Anonymous

    Complete speculation here, but Citrix may be one of the new SaaS monitored apps. SaaS monitored apps can be monitored via the cloud collector instead of running from an on-prem collector in your environment. Go to the exchange and look for the "Cloud Integrations" tab. If you don't have it, reach out to your CSM.

  • It was on my Citrix Cloud logon for the last few months. Of course now it seems to have disappeared. Wondering if they decided to hold off. 

    At a high level things were moving from customer.xendesktop.net to https://api-us.cloud.com/monitorodata with different references. I see mention of it all here:

    Accessing Monitor Service Data in Citrix Cloud

    • The "https://{Customer_Id}.xendesktop.net/Citrix/monitor/odata/v4/data" URL is replaced with "https://{ApiGatewayEndpoint}". The HTTP header "Customer" is now replaced with "Citrix-CustomerId".

     

  • 11 minutes ago, Brian Wagner said:

    Hi,

    Thanks so much for this awesome data source. I'm aware that Citrix is changing the API's for the Cloud monitoring in July and I believe these data sources will be affected. 

    Do you happen to be working on any updates to support the new method?

    Thanks!

    I wasn't aware of any API changes. Do you have a link?

  • Hi,

    Thanks so much for this awesome data source. I'm aware that Citrix is changing the API's for the Cloud monitoring in July and I believe these data sources will be affected. 

    Do you happen to be working on any updates to support the new method?

    Thanks!