-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Prometheus remote write exporter implement v2 #33661
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Thanks for the proposal @jmichalek132, makes sense to me. Agreed that a feature gate is a good idea here. 👍 |
Interesting! How can I contribute to this feature? @crobert-1 ,@jmichalek132 |
Remote write 2.0 is still experimental in prometheus, however it will be enabled by default in the the upcoming version version 2.54.0. Having said that I would welcome a contribution that will add support to PRW2.0. I think we can add a configuration option |
Thanks @rapphil . Will look into the Prometheus remote write 2.0 and plan the changes with above said |
cc @ArthurSens |
@dashpole Good to hear that this issue under CNCF Mentorship. Would like to contribute to this under LFX Mentorship. What could be application process to be part of applying to this project? |
Hi @varshith257, the application happens through the LFX website. There's a lot of instructions on their website :) |
@ArthurSens Thanks for pointing me there :) Right now will apply to this project. Any other tasks that has to be done before application apart from resume and cover letter? |
I don't think there's any other requirements :) |
Hello! @ArthurSens @dashpole @aknuds1 Apart from these, what do you suggest to try on to learn/test, relavant to this feature and also more generic to get involved with active code contributions in both the organizations. |
I think it should link to https://prometheus.io/docs/specs/remote_write_spec/. I would try out the existing PRW exporter with the prometheus server as a first step. There should be time to get familiar with the components after the internship starts if you are selected. |
Most open-source projects have community meetings and guidelines somewhere in their repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md https://github.com/prometheus/prometheus/blob/main/CONTRIBUTING.md These documents usually guide you in a good direction for code contributions :) It's also a good idea to look for issues labeled as |
Component(s)
exporter/prometheusremotewrite
Is your feature request related to a problem? Please describe.
Prometheus remote write v2 spec is close to being finalized, it would be good time to start working on implementing support for it in the prometheus remote write exporter component. Soon backend such as prometheus, mimir, thanos etc will start supporting it. It would great to start working on implementing to gain it's benefits,.
Describe the solution you'd like
I would like to contribute implementation of the remote write v2 prometheus/docs#2462 into the prometheus remote write exporter, most likely behind a feature flag since long-term v2 version is supposed to replace the current implementation.
Describe alternatives you've considered
Potentially it could introduced as a separate component but I hope that won't be necessary.
Additional context
The current implementation of remote write v2 lives in it's own branch of prometheus, https://github.com/prometheus/prometheus/tree/remote-write-2.0 , but should be merged soon.
The text was updated successfully, but these errors were encountered: