mirror of
https://github.com/urbit/shrub.git
synced 2024-12-19 16:51:42 +03:00
dfd744d08a
This actually raises difficult questions about the schema for the /vars peel. One level of nesting makes sense to aggregate per IO driver, but multiple levels is confusing. The current output is extremely unprincipled: you just have to know that there are multiple http servers and handle the output accordingly. Options would be: 1. collapse the ambiguity to the top level, i.e. 'http-0i8080', 'http-global', etc. 2. collapse the ambiguity to the inner level, i.e. '0i8080-connections'. 3. create a proper recursive data type that e.g. uses an $each. 3b. send some kind of schema. 5. recognize that we have entered a terrifying hall of mirrors and back out the entire approach of nested metrics in favor of just a bigass flat list of labels with values like borgmon does. |
||
---|---|---|
.. | ||
arvo | ||
base-dev | ||
bitcoin | ||
btc-wallet | ||
docker-image | ||
ent | ||
garden | ||
garden-dev | ||
grid | ||
herb | ||
hs | ||
interface | ||
landscape | ||
npm | ||
urbit | ||
urcrypt | ||
webterm | ||
symbolic-merge.sh |