I don't have any strong arguments for adding a node or consistency ID, but I'll 
give it a try:
1. Rolling update - while nodes have different versions, we'll be able to view 
information about their plugins. The set may differ depending on the connection 
to a specific node, and we need to keep this in mind. But we can ignore this 
since this operation will likely be quite rare.
2. In the plugin information, as I proposed with the new method 
PluginProvider#info, we can display information that may differ on different 
nodes, for example, depending on the distribution, data center, or some other 
information. Of course, this could be solved through metrics in a specific 
plugin or another system view.

If these arguments are weak and unconvincing, then I'll reject them; I suggest 
upvoting.

+1 for the node/consistent ID.

Reply via email to