Morten Siebuhr
Morten Siebuhr
It would be rather nice to execute something like the following: ``` git bisect start -- cardio --check "css.countByColor.#eee > 1" ``` Then it would find the revision between `good`...
Currently the `js.complexityReport` output 16 different metrics, both under "functions" and "aggregate" (16×2 = 32), whereon we calculate count, mean, max, std, mean_90th and max_90th (32×6 = 192 metrics). My...
We need at least one visualization built in (eg. ASCII spark-lines / canvas-output) for a proper wow-factor and instant gratification when new users try it out.
That would permit `cardio | cardio-report2array`. Alternately, we should just move the logic of `cardio-report2array` into `cardio`, so it would have the array-style output as the default one.
At time of writing, the interfaces are rather complex, poorly named and the design is generally haphazard.
Reading data from `expvar` would trivially allow other parts of the server to report internal metrics.
Graphite normalises several sequential dots to a single dot, ex: ``` foo..bar...baz ``` Becomes ``` foo.bar.baz ``` See https://github.com/graphite-project/carbon/issues/181
Graphites' docs says it works this way, and the parser should support that...
Something along the same lines of graphite-web, where a selection of a metric adds it (except if it's already there; then it's removed again). Mentrics should show up in text-fields...
The best explanation I could find is the description at https://github.com/brutasse/graphite-api. Blatantly stolen from the README: - `/metrics/find` - `/metrics/expand` - `/metrics/search` (removed strange `keep_query_pattern` parameter) - `/render` No-ops: -...