zipkin-php icon indicating copy to clipboard operation
zipkin-php copied to clipboard

Reporter can't provide feedback on success

Open jcchavezs opened this issue 5 years ago • 3 comments

Currently reporter is not providing any feedback about the call to the zipkin server, if it fails it logs the error and don't fail and more so if it success, it won't notify the user about it.

This is alright in normal situations but can be a bit obscure in tooling, for example: https://github.com/jcchavezs/jaeger2zipkin/blob/master/Main.php#L53

One option is to add a debug log line on success. Any ideas @anuraaga @adriancole @basvanbeek ?

jcchavezs avatar Oct 24 '20 18:10 jcchavezs

in java we use metrics for this, and the metrics handler could be overridden to use console if you wanted. granted in java, typically the underlying http libraries can log something so we don't have as much need to redo that.

putting logging on a common path can be tricky, so if you do be careful and guard it well so that it isn't on. normal users should not need to ever see this.

codefromthecrypt avatar Oct 25 '20 00:10 codefromthecrypt

We used to use metrics too but we dropped as none used and also it was hard to know what error was it (e.g. on debug as we are using curl underneath).

jcchavezs avatar Oct 29 '20 20:10 jcchavezs

as logging can flood the console, we only handle first error at warn level (this is in the async reporter) then FINE afterwards (similar to DEBUG level) https://github.com/openzipkin/zipkin-reporter-java/pull/155

codefromthecrypt avatar Nov 05 '20 00:11 codefromthecrypt