Open devinsba opened 5 years ago
Anyone have any thoughts on when we should feel comfortable calling this stable?
cc @llinder @adriancole @cemo @openzipkin/core
I think it is stable if the entry points to the SDK tracing and xray reporting are stable.
On Fri, 7 Dec 2018, 09:58 Brian Devins-Suresh <notifications@github.com wrote:
Anyone have any thoughts on when we should feel comfortable calling this stable?
cc @llinder https://github.com/llinder @adriancole https://github.com/adriancole @cemo https://github.com/cemo @openzipkin/core https://github.com/orgs/openzipkin/teams/core
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openzipkin/zipkin-aws/issues/117#issuecomment-445106373, or mute the thread https://github.com/notifications/unsubscribe-auth/AAD616fRECYTk0HAgUVmthXS6fxjHhMPks5u2dlNgaJpZM4ZGe8W .
With the SDK instrumentation finished I think this is a good time to summarize what we feel should be included or addressed before we release a version 1.0 of this library.
Existing issues
ErrorHandler
impl, and associated storage codePossible missing features
The following are features I can come up with by reading through the service list
FinishedSpanHandler
for tagging spans with host/container metadataTraceContext.Extractor
for Lambda requests from API Gateway45 DynamoDB storage support, this needs a champion and I don't think we hit rule of 3 on it either