-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[receiver/skywalking]Need to achieve the collection of metric data #20315
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Thank you for your proposal, which is also a feature I intend to implement soon. |
I'll be happy to implement this feature |
It's yours! @aheling11 |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
hi, @aheling11 How is it going? just friendly ping make this issue |
hi, after completing the first step of the code refactoring, I'm currently finishing up the remaining parts. :) |
hi, @aheling11 are you still working on the remaining parts? i have some needs for the skywalking jvm metric recently, if you are still working on it just ignore me or i can see what i can do for this issue |
@maokitty could you take this issue? |
I'm sorry for not following up on this for a long time. I have completed half of the remaining work and will submit a PR to merge the code into the main branch as soon as possible. |
Thanks for your contribution. I'm also looking for a receiver to collect some jvm metrics reported by skywalking SDK. Looking forward to next release! |
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Adding a JVM receiver in Skywalking and translate most of the metrics into the OpenTelemetry format according to the [OT JVM semantic conventions.](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/jvm/jvm-metrics.md) However, for the GC metrics, as the metric type is like gauge while the corresponding metric in the semantic conventions `jvm.gc.duration`is histogram type, I'm not translate it strictly according to the semantic conventions. **Link to tracking Issue:** <Issue number if applicable> #20315 **Testing:** <Describe what testing was performed and which tests were added.> test it locally. I export the metrics to Prometheus and display them in Grafana. <img width="1767" alt="image" src="https://github.com/open-telemetry/opentelemetry-collector-contrib/assets/30763743/97541490-d969-4a28-b5d8-87a04dd25b1d"> **Documentation:** <Describe the documentation added.>
…try#26315) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Adding a JVM receiver in Skywalking and translate most of the metrics into the OpenTelemetry format according to the [OT JVM semantic conventions.](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/jvm/jvm-metrics.md) However, for the GC metrics, as the metric type is like gauge while the corresponding metric in the semantic conventions `jvm.gc.duration`is histogram type, I'm not translate it strictly according to the semantic conventions. **Link to tracking Issue:** <Issue number if applicable> open-telemetry#20315 **Testing:** <Describe what testing was performed and which tests were added.> test it locally. I export the metrics to Prometheus and display them in Grafana. <img width="1767" alt="image" src="https://github.com/open-telemetry/opentelemetry-collector-contrib/assets/30763743/97541490-d969-4a28-b5d8-87a04dd25b1d"> **Documentation:** <Describe the documentation added.>
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I assume this feature is implemented with #26315 ? |
Component(s)
receiver/skywalking
Is your feature request related to a problem? Please describe.
I found that skywalking receiver can only accept tracing data, metrics like JVM runtime metrics are not supported. And opentelemetry already has a standard for JVM runtime metrics. It would be great if the skywalking receiver could also support metrics such as JVM runtime metrics and convert them into
otlp
metricsDescribe the solution you'd like
I noticed that the skywalking receiver has reserved the Collect interface for JVM metrics. Just implement the interface and translate the data format to otlp.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: