Open wu-sheng opened 3 years ago
I know we talked about ALS, which could be another separate feature. As general logs are more flexible, ALS is focusing on topology and traffic metrics analysising.
plugins interact
means passing trace context in the scope of a request. We can use ngx.ctx
to propagate it.skywalking tracer plugin
was enabled.plugins interact means passing trace context in the scope of a request. We can use ngx.ctx to propagate it.
Yes, it could be, but we should take care of the priority and execution sequence.
I think it is good to adopt SkyWalking native log format when skywalking tracer plugin was enabled.
I think we could include it in skywalking-nginx-lua repo if that makes senses to APISIX community.
APISIX has supported reporting access-log with trace context and error-log to SkyWalking by #5478 and #4633. So, I think this issue could be closed.
I think (1) is not supported? Do we skip it?
We can get tracing_context
in other plugins by ngx.ctx.tracing_context
. So I think (1) is supported as well.
I will submit a PR to add some explanations to the related document.
Thanks, look forward to that.
@dmsolr @moonming I want to discuss an enhancement feature for APISIX ecosystem about observability.
SkyWalking built its native tracer implementation for Nginx and APISIX, so we have this, http://apisix.apache.org/docs/apisix/plugins/skywalking/. Which supports tracing and backed by OAP's analysis capability, we have topology with metrics about traffic.
Now, with the latest SkyWalking's log analyzer, we should consider looping logs in. So 2 questions should be answered
If you feel interests, let's work on this together.