We use node_meta/node-meta to register some key/value-pairs like description("frontend") or environment (dev, integration, qa, ...) that are valid for whole nodes. Quite similar to #4173 we would like to use this node specific metadata in the ui.
A search filter in the node view "show me all nodes with value X" is the preferred version. For our needs this does not have to be a full blown search engine like "A=foo && key B=bar". A full text search for "foo" is fine (to us), if it is easier to implement. This could be different in larger environments. Being able to see it at all (raw json or anything like that) e.g. in the node-specific view would be a nice start. This would make it way easier to get some first hints what this server is doing while using the node view and will be a great help, if you want to drill down to some data, when you know the metadata like "frontend".
Hey @bwaterkamp !
Thanks for the feature request! This is definitely something we have been chatting about amongst the team.
Our first objective was to reproduce the old Consul UI on a more modern codebase with an updated look and feel, whilst keeping new features to a minimum during this 'phase'.
I think we are now past that, so we are into a second 'phase'. Therefore you'll begin to see some of these new features make their way into the new UI over time. Features are likely to be added on a similar cadence to the main Consul binary releases so when I say 'over time' that might give you an idea of how regularly these new features are likely to be added.
I'll try to keep you updated here on this specific feature.
Hi @bwaterkamp
Just a quick update here, as of Consul 1.6.0 node meta data (and service meta data) is visible in the UI (read only). Just to keep you in the loop, there is work progressing on using this data for searching in the UI. We've recently added more powerful search features to the Consul API so we will be using those to surface this in the UI.
Thanks!
Hi @johncowen
We pushed 1.6.1 to one of our development environments: This is definitely heading into the right direction (for us)! Thanks for your update!
Hey there,
We wanted to check in on this request since it has been inactive for at least 60 days.
If you think this is still an important issue in the latest version of Consul
or its documentation please reply with a comment here which will cause it to stay open for investigation.
If there is still no activity on this issue for 30 more days, we will go ahead and close it.
Feel free to check out the community forum as well!
Thank you!
Just a Ping for stalebot
Most helpful comment
Hey @bwaterkamp !
Thanks for the feature request! This is definitely something we have been chatting about amongst the team.
Our first objective was to reproduce the old Consul UI on a more modern codebase with an updated look and feel, whilst keeping new features to a minimum during this 'phase'.
I think we are now past that, so we are into a second 'phase'. Therefore you'll begin to see some of these new features make their way into the new UI over time. Features are likely to be added on a similar cadence to the main Consul binary releases so when I say 'over time' that might give you an idea of how regularly these new features are likely to be added.
I'll try to keep you updated here on this specific feature.