Closed codefromthecrypt closed 8 years ago
If there's an 'error' annotation, should there be a 'warning' annotation too?
@virtuald this might be of interest: http://dave.cheney.net/2015/11/05/lets-talk-about-logging. Basically, it argues that most log levels are an anti-pattern.
I have mixed feelings about that article.
since it takes a bit of effort to try and get instrumentation to use any new annotations, and this is the authoritative definition of core, I'd argue for only "error" at the moment.
Error is much harder hitting, and explains more about latency than warning I think, yet doesn't prevent us from doing warning later if it becomes popular.
SG?
Sure.
clarified docs based on comments
This adds an error constant used to flag spans as such.
See https://github.com/openzipkin/zipkin/issues/1140