-
Notifications
You must be signed in to change notification settings - Fork 245
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
Zig SIG: current level of interest? #2514
Comments
I would be interested and happy to help. |
I tried to develop a toy implementation of the OpenTelemetry by Zig that is cited above, and I was invited to this forces by @inge4pres (thanks a lot!). |
work in progress is happening in this repo https://github.com/zig-o11y/opentelemetry-sdk |
@inge4pres @kakkoyun @Drumato thanks for raising this issue and your interest in creating a Zig SIG. If you are serious about this endavour, please take a look into the following document that outlines how you can get started with a new project: https://github.com/open-telemetry/community/blob/main/project-management.md |
Hi @inge4pres , Seems am little late to the party, just wanted to express my interest for this project and would be happy to help on the associated topics. Would be great if I can be taken up. Bit about me: Do let me know if I too can provide any support to your repo. Thank You! |
Hey there folks 👋🏼
This card is up to gauge interest in maintaining a Zig implementation.
Zig is a language that is fully inter-operable with C, so producing an API and an SDK in Zig enables Zig and C programmers to onboard OpenTelemetry signals in their applications.
At first, the purpose of this groups would be:
Optionally further on, the building blocks listed above and created along the way could be used to complement auto-instrumentation and other parts of OpenTelemetry written in languages speaking the C ABI (BPF-based agents, CGO for Go, Rust FFI, CPython, etc...), because of how Zig compiles to C and BPF natively.
Downside: Zig is not 1.0 yet, so there may be some additional maintenance effort in keeping up to date the code with the language releases.
Currently, there is work-in-progress in unofficial implementations for metrics and traces.
If anyone is interested in progressing this work, please introduce yourself and let's chat :)
The text was updated successfully, but these errors were encountered: