Re-architect /status rest endpoint
psyomn opened this issue · 0 comments
psyomn commented
For example, there should be a better way to store everything instead of lumping everything into one big mudball map, that is accessed on /status
There should be things like /status/group1
, /status/group2
etc.
- There should be one status server for many data caches