I’m the developer on BigFix Asset Network Maps, and yes, your 1100+ relays is probably the cause. Each relay is given its own node in the graph, and 1100 nodes is pushing the capabilities of the dashboard, even before you consider all the subnet nodes that must be in the graph as well.
We meant to post some limitations on the sizes of deployments that the dashboard would work for, but we seem to have forgotten to do that. Unfortunately, your deployment would probably not be supported.
Could the tool be adapted to take large deployments into consideration? It is useful and interesting data. It would be a shame to not be able to take advantage of it.
Could you have different settings for small, medium, and large organizations that, for example, varied the refresh rate and/or other calculations to accommodate different architectures?
It’s certainly something we want to do in the future, and I’m glad to hear you see value in the data. Unfortunately, for this dashboard there’s no easy fix for the problem of scalability.
That said, we’re in the process of determining the future of the BigFix Asset Network Maps dashboard, and improving the scalability has been a central point of discussion. I can’t make any guarantees about whether we’ll be able to support your deployment in the future, but it’s very helpful to know that there’s interest in getting the dashboard working at that size.
I downloaded and added it to my site but has been sitting at the Gathering BigFix Asset Network Maps. Waiting for server to begin Gather for a long time…