Forum Discussion

Gjon's avatar
Gjon
4 years ago

Citrix Cloud Monitoring

Installation

  1. 1. Install the package from LM Exchange "Citrix Cloud"
  3. 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!

  • Gjon's avatar
    Gjon
    4 years ago
    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.

  • Vitor_Santos's avatar
    Vitor_Santos
    Icon for Advisor rankAdvisor
    3 years ago

    Bumping this again...

    Where can we find the property source for the cloud connector 'Locator JYW9D7'? @Gjon can you advise? I'm no longer able to search using the locator code on our portal.
    I see another used asked for this a few months ago but no further comments after it.

    @Stuart Weenig / @Michael Rodrigues is there any other alternative to find custom modules on exchange? Since the locator code prompt no longer appears & we're directly redirected to exchange.

    Already reached out to our CSM as well to confirm if there's any ETA for this cloud integration.

  • Don_OKeeffe's avatar
    Don_OKeeffe
    2 years ago

    Hello All,

    I am also not able to locate and Install Cloud Connector property source: Locator JYW9D7

    Can anyone help the number of people who asked on this page how to do this now?

    Many thanks

  • Anonymous's avatar
    Anonymous
    2 years ago

    As far as I can tell (still not sure if i'm using the new exchange right), that module doesn't exist on the exchange anymore.

  • Manaf_K's avatar
    Manaf_K
    2 years ago

    Hi Dorian,

    Thanks for your reply!

    I don’t intend to modify the token but how\where the token is being retrieved.

    I got the below notification, and interpret that this Citrix Cloud DataSource would stop working after 30th June.

    At present, it all works without any issues. But would stop after 30th June 2023

    The new endpoint information from Citrix can be found here : https://developer.cloud.com/citrix-cloud/citrix-cloud-api-overview/docs/get-started-with-citrix-cloud-apis.

    Thanks

  • Magna_FL's avatar
    Magna_FL
    2 years ago

    Hello - i had the same issue with the Service URL Error - looking into the Scripts i found that not all Query are set correct after changing to the new API Gateway. However i just get good results for the DaaS Service like Sessions active etc. Other Queries like Logon Perf. etc. brings back no Data.

  • Manaf_K's avatar
    Manaf_K
    2 years ago

    Hi @Magna_FL

    If you are referring to the DS LogonPerformance, the URI and query would have to be modified.
    you need to remove “data” from the query path.

    For instance, LogonPerformance DS -
    the modified URI would be - "https:/api gateway/monitorodata" + query
    and modified query would be - "/Sessions?\$filter=EndD and so on……..” - without the word “data“ in the path.

    You can refer this link that lists the available api gateway data sets,
    https://developer-docs.citrix.com/en-us/monitor-service-odata-api/current-release.html#urls-for-available-data-sets.

  • DavidK's avatar
    DavidK
    Icon for Neophyte rankNeophyte
    2 years ago

    Hello, Looking at the Citrix_Cloud_DeliveryGroups datasource, does anyone know why the max TotalMachines shown is 100 even though we have a total of 1800?  

    Thanks,

    David

  • Magna_FL's avatar
    Magna_FL
    2 years ago

    Hello, Looking at the Citrix_Cloud_DeliveryGroups datasource, does anyone know why the max TotalMachines shown is 100 even though we have a total of 1800?  

    Thanks,

    David

    Hello David, i have the same issue. I think its more related to the API just giving you the first 100 results. I have changed the queries a bit that he is paging the results but still i get 100 as Total Machines in the DG

  • DavidK's avatar
    DavidK
    Icon for Neophyte rankNeophyte
    2 years ago

    Thanks Magna, I will keep amending the script to see how far I can get.