Hi Alexander,

one way to achieve this would be to create User-Defined APIs on source cluster, and then to call those APIs from GQI DS on destination cluster.

We've recently worked on similar solution and there are a few caveats to consider:

• You have to define which data the API would return, and you have to build it on source cluster.
• User-Defined APIs use token for authentication and you have to decide how you will store that token in the GQI DS on destination cluster. Regardless of how you decide to store it, the best practice would be to create user with VERY limited access and to use that users token.
• You will have to implement HTTP communication yourself, you can use native .NET HTTPClient though.
• Web Services provide wide range of possibilities to interact with source cluster as well, depending on your needs you might not need to use User-Defined APIs.

Hope this helps and let me know if you have any further questions,
Cheers

Hi Alexandre,

Depending of your use case, I believe there are two possible options:

• In case you plan to retrieve specific information from the cluster, the option described by Edib will be a good approach. Something to keep in mind is that the every time that you open a dashboard in the destination cluster, the GQI query will be triggered requesting data from the source cluster. For example, if there will be multiple users opening this dashboard, the GQI query will be executed multiple times. You will need to see if a cache mechanism is required.
• In case you plan large amount of data (e.g. the list of all amplifiers available on your cluster, the peak value of a KPI from the last 24 hours), then you could use Data Aggregator. Data Aggregator can execute GQI queries in the source cluster (in a scheduled way) and store the result in a CSV file (in the destination cluster). Then the dashboard in the destination cluster will read the content of the CSV file. In that way you avoid retrieving data from the source cluster every time that you open a dashboard in the destination cluster.

Hope it helps.