-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
l2met supports one-time event syntax #84
Comments
@ryandotsmith What's a sane format for me to suggest Add-on providers use? How about the following:
This is inspired by the Librato docs that @josephruscio mentioned. |
@mattonrails nice. One quick observation... The time is included in the syslog packet's header per RFC5424. So it is not necessary to include a start_time as long as the emitter emits the log line when the event actually started. |
Man, so excited to get Heroku's deploy events on this syntax. I am dying to have my dyno restart and deploys annotated on my charts. |
+100 :) |
Love the idea. |
Suggestion for syntax, if timestamp isn't needed, and to be more consistent w/ existing metric syntax:
E.g. in the case of Heroku deploys, could be a release number:
This is a nice and terse syntax, but is obviously limiting if you want to associate more info. But that's the trade-off l2met has already taken with its existing metric syntax. |
Many metric systems support the concept of correlating one-time or aperiodic events against their metrics, commonly as vertical lines overlaid on a line chart (e.g. Librato Annotations)
An example of such an event is Heroku's release notifications that occur whenever new code is pushed to a Heroku application:
l2met should support a format for parsing events from the log stream and pushing them to the metrics backend. This ideally would support a rich event type e.g. Librato's Annotation definition. /cc @nextmat @mheffner
The text was updated successfully, but these errors were encountered: