Add predict_linear exploration blog#2947
Conversation
nwanduka
left a comment
nwanduka
left a comment
There was a problem hiding this comment.
Thanks for sharing this, @OpeOnikute. I’ve added a few missing commas. Otherwise, LGTM. I think it’s ready to merge, but I’ll let the docs bug scrub team review it tomorrow (if they get to it) before publishing.
Signed-off-by: Opeyemi Onikute <opeyemionikute@yahoo.com> Co-authored-by: Victoria Nduka <122698422+nwanduka@users.noreply.github.com> Signed-off-by: Opeyemi Onikute <opeyemionikute@yahoo.com>
OpeOnikute
force-pushed
the
opeyemi/predict-linear-blog
branch
from
fe73094 to
39016b6
Compare
|
Hi @nwanduka, thanks for the suggestions. I've added them in and squashed the commits. Can we get this merged? |
|
@beorn7 when you get the chance, could you please review this post for technical accuracy and merge if everything looks good? Thank you |
|
@OpeOnikute thanks for writing this. @nwanduka thanks for shepherding this. Sadly, I won't have time for reviewing this. There are just a few work days left for me before I retire from the project, and I still have to wrap up some loose ends only I can wrap up. There are, however, many qualified reviewers for this blog post among the maintainers. |
|
Thanks for responding, @beorn7. No worries. Happy retirement 🎉🚀 |
|
Hello, who can review this? |
|
Bumping again. Is there anyone on the docs team that can tell me what to do next here? |
|
Hey @ArthurSens, could you please review this? Or if it’s outside your scope, could you point me to the appropriate maintainer? |
|
Hey Victoria, unfortunately, we don't have a maintainer dedicated to PromQL at the moment. I just verified here: https://github.com/prometheus/prometheus/blob/main/MAINTAINERS.md When we don't have a dedicated maintainer for a specific part of the codebase, the "General maintainers" are usually responsible for that part. That said, they are usually overloaded and focused on the codebase itself, not really on our website or on how PromQL is documented. Sorry for the bad news, but I don't think our team is well structured to receive blog contributions from external contributors at the moment. This is not ideal, but we need an internal org restructure before we can commit to reviewing this kind of contributions 😞 |
|
maybe something to discuss during the docs working group @jan--f |
|
Thanks Arthur. I did raise this with Jan at a past docs meeting and he suggested discussing it at the next DevSummit (last month). Unfortunately, I couldn't attend, and, judging by the meeting notes, I'm not sure we got around to it. Hopefully, we get to it in the upcoming one. @OpeOnikute, apologies for the delay on this. It may sit for a little while longer until we find the right reviewer, but please know your contribution is appreciated. We just want to make sure everything is properly reviewed before it goes up on the blog. Thank you for your patience and for putting in the work on this. |
4 participants
As discussed in #2861, this pull request adds a blog post describing predict_linear and how it works. The main difference between the original proposal and this one is that I did not go into the full details of ML (regression vs. classification) because I don't consider it relevant to the Prometheus blog. Instead, the article focuses on only what is needed to understand how predict_linear itself works and what the current limitations are.
Open to feedback!