3 ms·
This looks great. I use a modified version of gdash, but always wish that the graphs were rendered in D3 instead. At first glance, it seems like the configura
by moxie 14y ago
This looks great. I use a modified version of gdash, but always wish that the graphs were rendered in D3 instead.
At first glance, it seems like the configuration could be a little more expressive for some common use cases. For instance, it seems pretty typical to build graphs that are collections of stats from different regions/instances from a set of metrics that have the form: stats.<machine/region>.specific_stat.
One nice thing about gdash is the ability to define a list of instances/regions and their readable name mappings, which you can then easily build multiple graphs for different stats using.
Seems like that'd be a little trickier here.
- gingerlime 14y agoThat's an interesting idea. I'd have to take a closer look at the gdash dsl and see if I can borrow/steal some ideas. Can you please explain the difference between this and using the built-in graphite target wildcards? e.g. you can specify stats.*.specific_stat and graphite (and giraffe) will output all matching targets for you. Another alternative is stats.{one,another}.specific_stat Those work 'out-of-the-box' with graphite and giraffe currently. Or are you talking about something different?
- moxie 14y agoI need to be able to define consistent labels and colors for machines across multiple graphs. So a machine named 'uk' is always displayed 'London' in dark green, consistently across all graphs.
- gingerlime 14y agohmmm... I can see why this would be useful. Not entirely sure how is best to implement such a thing. Perhaps it's better to open a github issue so this can be discussed properly rather than here?
- gingerlime 14y agoThis should now be supported with Giraffe.