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 🎉🚀 |
3 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!