Implementing drawAsInfinite function about grafana

[jdoupe]

So.. um. While annotations are great, what became of implementing drawAsInfinite? Still would be useful.

[torkelo]

Yes, absolutely! I already have a proof of concept branch for events / annotations. This feature should be available in the coming 2 weeks!

[torkelo]

I am thinking that annotations should be general feature, where data for annotations can come from graphite metrics (analog for drawAsInfinite ) , graphite events, or events stored in elasticsearch. Annotations should be graph specific, or global for the whole dashboard (appear on every graph) or global for every dashboard (so only need to define them once). And be toggleable (so you can choose if you want to see annotations or not)

[nemenemsrouge]

This would be sooooo great!

[nemenemsrouge]

hello!
I am waiting impatiently for this feature. Have you got any news about it?

[torkelo]

should be done sometime this week. What should be prio source for annotations? I have only gotten graphite metrics as source working, next up might be graphite events (does anyone use them?) or events stored in elastic (like https://github.com/Dieterbe/anthracite)

[torkelo]

Also first I think I will add global annotations defined in config.js first (so they can be reused on all dashboards graphs). Looks like this now:

Just a icon at the time of the annotation, hover over the icon gives you event metadata. I am not 100% happy about it, might want some option for another kind of visualization (like drawInfinite line, or the event name printed on the graph).

[jippi]

Would be nice if the annotations could be any source of API (json) that can return the correct format

Different dashboards most likely would need different annotation sources anyway

So perhaps have it as a Dashbord configure setting as well

[ctrlok]

Now anthracite is best way to store events. I using it with graph-explorer and it is very useful.

[nemenemsrouge]

Hi already use graphite events with drawAsInfinite. They are pretty usefull since you could tag them.

[torkelo]

@nemenemsrouge you mean you use standard metric keys as events? with graphite events I mean the "experimental" graphite events feature which I thought was only supported by the graphite included flot renderer. drawAsInifinte is only just a simple vertical line right? what do you mean "tag them" ?

[nemenemsrouge]

Ok,

I actually use graphite events.
I found some documentation here: http://obfuscurity.com/2014/01/Graphite-Tip-A-Better-Way-to-Store-Events

so curl -X POST "http://graphite/events/"
-d '{"what": "Event - deploy", "tags": "deploy,tag2,tag3",
"data": "deploy of master branch happened at Fri Jan 3 22:34:41 UTC 2014"}'

This will create an event with 3 tags linked (deploy, tag2, tag3)

Then in the graphite GUI I use this kind of request:
alias(drawAsInfinite(events('deploy')), 'My events')

this will render a vertical line at the date of each event matching the TAG "deploy". BUT with the standard graphite GUI, the metadata are not used/displayed

[torkelo]

I have created a new issue for further improvements to annotations and feedback:
#133

[vxe]

I find annotations to cumbersome to use in practice for multiple datasources, especially considering I could use one query with drawAsInfinite and wildcarding to avoid the problem all together. For example I need a dashboard with 20 data sources, and have to implement my event markers as 20 annotations

[theanine]

I need per-graph annotations (or ideally, drawAsInfinite)

[misaunde]

+1 on implementing drawAsInfinite