Dieter Plaetinck

somebody requested this on irc today. basically stack targets on a graph, but at each point in time, rescale all samples so that they all add up to a given...

make catchall bucket optional

3

it should be possible to choose whether you want a catchall bucket or not. i think this makes sense for both aggregation and grouping. a simple syntax and implementation could...

alerting expressions always start with the base unit irrespective of the requested unit

2

let's say I want to alert on the amount of GB free of /var on my graphite machine. I enter the query "unit=GB type=free graphite3 var" because of #69 we...

need to update unit and target_type when we do things such as deriving and integrating

1

this probably already mostly works, but not all cases. for example a target with unit=Pckt, target_type=counter (a statsd packets received metric), when I query for unit=Pckt/s it shows up with...

unify dashboards with default interface, use proper javascript framework

1

dashboards should be: - editable through web UI(add/remove queries, edit queries, set default value for apply to all) - saveable and loadable through web UI the default interface: - should...

when you have multiple metrics that all have tags n1,n2,...n5 (some have n6 and n7, not sure yet if this matters). say you want to have 1 graph, and all...

slowness when rendering a graph with a lot of targets

4

if you didn't filter down a lot, it can happen that graphs contain hundreds of metrics. - due to the grouping, there's basically no limit to how many targets appear...

document features introduced in #59

2

- [ ] extended regex syntax (with the specifics of anchoring) on [GEQL wiki page](https://github.com/vimeo/graph-explorer/wiki/GEQL) - [ ] automatic derivation for counters, wraparound/max_value tag, how to prevent it - [...

to make sure, for different GEQL features, we get the correct results from ES. not sure what's the best way to do this.

for avg by, sum by, and group by which allow patterns for buckets, show them in query explanation section