zipkin-aws
zipkin-aws copied to clipboard
openzipkin
Release 1.0 Todo List
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
- [ ] #60 Add an XRay
ErrorHandlerimpl, and associated storage code - [ ] #73 Add better hooks to XRay storage to allow RPC instrumentation to map nicely
- [ ] #108 XRay configured sampler
- [ ] #116 Intermediate error handling on V2 SDK Instrumentation
Possible missing features
The following are features I can come up with by reading through the service list
FinishedSpanHandlerfor tagging spans with host/container metadataTraceContext.Extractorfor Lambda requests from API Gateway- Service specific tags in SDK instrumentation for Dynamo and SQS (for XRay support)
- #45 DynamoDB storage support, this needs a champion and I don't think we hit rule of 3 on it either
- SNS, SQS, and Kinesis propagation handlers (smarthings have built the first 2
- Kinesis Streaming Dependencies job (we attic-ed the first one)
- MQTT propagation that supports AWS IoT
- A tool for extracting XRay data to add into Zipkin (API Gateway, Lambda)
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 <[email protected] 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 .
