ciaranj / chartled Goto Github PK

Currently the charts imply that you can have more than 1 vertical axis. Currently you can't. Need to fix that.

The current movingAverage function assumes 'null' for data before the 'from' on the target, ideally we'd 'back fetch' the data if present to bootstrap/initiate the movingAverage

Currently the bar style in particular means that for a given time point a lower value on the vertical axis will be obscured by a higher value (as it will be over-written).

Really the bar style needs to render each time series point individually rather than within the 'layer' itself :/

The current list of all metrics when editing a chart is not-fit-for-purpose. As an interim measure we could make it a filtered drop-down in some manner so the list can be reduced/searched by typing (and not by scrolling, which it turns out doesn't work with track-ball users!)

Performance improvement for charts with large number of 'empty' bars.

According to the canonical definition of all things awesome (the graphite docs [http://graphite.readthedocs.org/en/latest/render_api.html ]). Ranges within metrics should behave as follows:

Characters in square brackets ([...]) specify a single character position in the path string, and match if the character in that position matches one of the characters in the list or range.
A character range is indicated by 2 characters separated by a dash (-), and means that any character between those 2 characters (inclusive) will match. More than one range can be included within the square brackets, e.g. foo[a-z0-9]bar will match foopbar, foo7bar etc..
If the characters cannot be read as a range, they are treated as a list - any character in the list will match, e.g. foo[bc]ar will match foobar and foocar. If you want to include a dash (-) in your list, put it at the beginning or end, so it’s not interpreted as a range.

They don't currently, ie.
foo.[12].bar
Would match foo.12.bar, whereas it should only match foo.1.bar or foo.2.bar

Nor do A-Z style ranges seem to work.

movingAverage works by calculating the moving average of a metric (or metrics) over a time interval.

movingAverage(Server.instance*.threads.idle,'5min')

movingAverage needs to 'intelligently' back populate data at the start based on the 'stack' passed to it. I.e. if we pass a 'timeShift' or 'scale' to movingAverage it needs to ensure that 'timeShift' or 'scale' return enough data such that the moving average can be calculated accurately.

TimeShift function would be damn handy!

Cannot view text when adding a textbox and cannot edit the contents, resize etc.

Currently cannot stack lines, areas or bars. (Solving this is potentially quite interesting, as you want to order the series optimally, whilst making sure the colours for the associated metric don't change if the visual rendering order changes.)