Skip to content
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

Open
1 task done
leopardrota opened this issue May 10, 2023 · 6 comments
Open
1 task done

[Question] About eventmesh-trace-plugin module #3895

leopardrota opened this issue May 10, 2023 · 6 comments
Labels
question Further information is requested Stale

Comments

@leopardrota
Copy link

leopardrota commented May 10, 2023

Search before asking

  • I had searched in the issues and found no similar issues.

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的整体工程?
希望社区能回复下。

@leopardrota leopardrota added the question Further information is requested label May 10, 2023
@github-actions
Copy link
Contributor

Welcome to the Apache EventMesh community!!
We are glad that you are contributing by opening this issue. :D

Please make sure to include all the relevant context.
We will be here shortly.

If you are interested in contributing to our project, please let us know!
You can check out our contributing guide on contributing to EventMesh.

Want to get closer to the community?

WeChat Assistant WeChat Public Account Slack
Join Slack Chat

Mailing Lists:

Name Description Subscribe Unsubscribe Archive
Users User support and questions mailing list Subscribe Unsubscribe Mail Archives
Development Development related discussions Subscribe Unsubscribe Mail Archives
Commits All commits to repositories Subscribe Unsubscribe Mail Archives
Issues Issues or PRs comments and reviews Subscribe Unsubscribe Mail Archives

@mxsm
Copy link
Member

mxsm commented May 10, 2023

@leopardrota

  1. The eventmesh-trace-plugin module is mainly used for link tracking. If you look at the code, you will find that it is mainly used in the runtime module.
  2. The eventmesh-trace-plugin has an API module that is mainly based on the OpenTelemetry Trace specification. As for pinpoint and Zipkin, OpenTelemetry Trace only imports data into different services. For details, please refer to the official website of OpenTelemetry.

The community is also further improving the official website’s documentation. Of course, contributions to the community’s documentation or code are welcome.


  1. eventmesh-trace-plugin这个模块主要是用于链路跟踪,你看代码就会发现这个主要用在runtime模块里面。
  2. eventmesh-trace-plugin有一个API的模块主要是基于OpenTelemetry Trace规范做的。而对于pinpoint以及Zipkin只是OpenTelemetry Trace将数据导入不同的服务,具体可以参照OpenTelemetry的官网文档

对于官网的文档社区也在进一步完善当中,当然会也欢迎给社区贡献贡献文档或者代码。

@leopardrota
Copy link
Author

leopardrota commented May 10, 2023

@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?


非常感谢您的回复。
所以eventmesh-trace-plugin模块采集的链路数据是流经runtime模块的流量(可能来自eventmesh自身,也可能来自所在的应用工程),对吗?
所以有了eventmesh-trace-plugin模块,链路追踪数据要传到zipkin或者pinpoint,是不需要额外安装zipkin客户端或者pinpoint客户端的,对吗?

Copy link
Contributor

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.

@github-actions github-actions bot added the Stale label Apr 22, 2024
@Pil0tXia
Copy link
Member

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?

Only events delivered by current EventMesh Runtime instance will be traced.

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?

No, a zipkin instance is required to collect data.

@github-actions github-actions bot removed the Stale label Apr 23, 2024
Copy link
Contributor

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.

@github-actions github-actions bot added the Stale label Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Stale
Projects
None yet
Development

No branches or pull requests

3 participants