@Shubhadip Pal Thanks for posting this topic here.

I see that you are not getting metrics from secondary cluster in the Multicluster manager dashboard.

This doesn’t seem to be role and permission related.

Would you be able to access primary k10 prometheus and look at the targets ?

<k10URL>/k10/prometheus/targets

Do you see any targets with the name of your secondary clusters ? what is the status of the target ?

Hi @jaiganeshjk , I am getting this window for the URL you said, not sure which cluster data is showing in this page.

Can you scroll down in the same page, You should see a Target (similar to the one that says httpServiceDiscovery in your screenshot) with your secondary cluster name. 

Do you see it failing to discover with an error or is it missing  ?

I see the lower page as below.

@Shubhadip Pal Thanks. This means that the prometheus doesn’t have the federation config.

Just one more question for me to understand why the prometheus doesn’t have the federation config.

Are you using K10 operator based installation for your primary K10 instance ?

yes, we did operator based installation.

Oh. Then I might have an idea what might be the issue.

It could be because the operator might remove the federation config from the prometheus configMap after the bootstrap of the secondary is completed. 

One thing we could do is to wait for the next release 6.5 to resolve this issue.

From the new release, K10 will not be relying on the prometheus federation to get the metrics from the secondary clusters. It will use a different messaging mechanism to get the metrics from the secondary cluster going forward. So this issue will get automatically resolved with this.

Still I will file an issue internally with the engineering to look into this.

Thanks for the update. Anyways, we can select  secondary cluster from drop down list and browse into individual cluster.