Consider exposing a logger interface to log errors within the pipeline class
How can we catch/take action on ErrDropped, it doesn't seem to be bubbled up anywhere outside the class. ServeHTTP method calls it without looking for if there was an error and to my knowledge this doesn't get bubbled up to the HTTP server class (which does expose a logging interface)
I'm the first to admit i'm not the most advanced golang user, so let me know if i'm missing some implimentation detail that obviates the issue. I plan to impliment this at relatively large scale and knowing when we start dropping reports is going to be very valuable to log to our elastic stack.
https://github.com/google/nel-collector/blob/6f38d97d2d5cce5625e4c139cdf3c5580fa8914e/pkg/collector/pipeline.go#L167
This issue is comprised of 2 points:
I'm the first to admit i'm not the most advanced golang user, so let me know if i'm missing some implimentation detail that obviates the issue. I plan to impliment this at relatively large scale and knowing when we start dropping reports is going to be very valuable to log to our elastic stack.
Thanks!