You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you select the output of the http interface of orchestrator and look at: http://xxx:3000/web/status you see a list of the orchestrator nodes. While not alway absolutely important there is no vision here of which version each node is running. Most of the time you'd expect them to be the same but if you run more than one node then being able to see this explicitly would be good.
So I would like to see added to the list of available nodes a couple of extra columns:
the version of orchestrator that is running
the port on which it is listening. That may be expected to be the default but may not be. If proxies are involved or load balancers then this may not match the actual port you are connecting to.
the uptime of each node in a human readable format. Again it's convenient to see if (all) nodes have been running for the same time.
None of this may be desperately urgent but it is handy to have.
The text was updated successfully, but these errors were encountered:
sjmudd
pushed a commit
to sjmudd/outbrain-orchestrator
that referenced
this issue
Dec 27, 2016
If you select the output of the http interface of orchestrator and look at: http://xxx:3000/web/status you see a list of the orchestrator nodes. While not alway absolutely important there is no vision here of which version each node is running. Most of the time you'd expect them to be the same but if you run more than one node then being able to see this explicitly would be good.
So I would like to see added to the list of available nodes a couple of extra columns:
None of this may be desperately urgent but it is handy to have.
The text was updated successfully, but these errors were encountered: