-
Notifications
You must be signed in to change notification settings - Fork 639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] About eventmesh-trace-plugin module #3895
Comments
Welcome to the Apache EventMesh community!! Please make sure to include all the relevant context. If you are interested in contributing to our project, please let us know! Want to get closer to the community?
Mailing Lists:
|
The community is also further improving the official website’s documentation. Of course, contributions to the community’s documentation or code are welcome.
对于官网的文档社区也在进一步完善当中,当然会也欢迎给社区贡献贡献文档或者代码。 |
@mxsm Thank you very much for your reply. So the link data collected by the eventmesh-trace-plugin module is the traffic flowing through the runtime module (which may come from the eventmesh itself or the application project it is in), right? So with the eventmesh-trace-plugin module, if link tracking data needs to be transmitted to zipkin or pinpoint, there is no need to install an additional zipkin or pinpoint client, right? 非常感谢您的回复。 |
It has been 90 days since the last activity on this issue. Apache EventMesh values the voices of the community. Please don't hesitate to share your latest insights on this matter at any time, as the community is more than willing to engage in discussions regarding the development and optimization directions of this feature. If you feel that your issue has been resolved, please feel free to close it. Should you have any additional information to share, you are welcome to reopen this issue. |
Only events delivered by current EventMesh Runtime instance will be traced.
No, a zipkin instance is required to collect data. |
It has been 90 days since the last activity on this issue. Apache EventMesh values the voices of the community. Please don't hesitate to share your latest insights on this matter at any time, as the community is more than willing to engage in discussions regarding the development and optimization directions of this feature. If you feel that your issue has been resolved, please feel free to close it. Should you have any additional information to share, you are welcome to reopen this issue. |
Search before asking
Question
About eventmesh-trace-plugin module, I would like to have a comprehensive understanding of its functions first. Due to the relatively simple documentation on the official website, I still don't know the functionality of this module after reading it.
I have two questions:
1: Three types of plugins should be similar. Such as Pinpoint, this plugin allows users to send trace data to the Pinpoint server directly through eventmesh without installing Pinpoint's client, right?
2: Is the trace data collected by this module only internal eventmesh? Or the overall project of eventmesh?
Looking forward to a response from the community.
想先整体了解下eventmesh-trace-plugin模块的功能。由于官网上文档略简单,看了以后依然没明白该模块的功能。
我的疑问有两个:
一:三种插件应该都差不多吧,比如pinpoint,该插件可以使用户不用安装pinpoint的客户端,直接通过eventmesh就能将trace数据发送到pinpoint服务端,是这样吗?
二:该模块采集的trace数据只是eventmesh内部的?还是使用了eventmesh的整体工程?
希望社区能回复下。
The text was updated successfully, but these errors were encountered: