I'd like to post a certain set-up I'm using; a combination of prometheus, k8s, helm and some other related tooling. The goal is scraping metrics (of common software like node_exporter and custom software) from "IoT" devices. It's a set-up that's been working for a while, but I'm hitting some pain points that I don't know how to solve. I'd like to explain the reasoning behind the original decision to use this set-up, the pain points currently surfacing and then ask for feedback and opinions on what to do next.

Is the code review stack exchange site an appropriate place to ask this? I couldn't find any tags related to prometheus, k8s or helm so I'm not sure if these more DevOps oriented questions belong here. If not, I would really appreciate any answers that can point me in the right direction.

  • \$\begingroup\$ Regardless of whether the tools your are using are on-topic or not your question likely isn't. "I'm hitting some pain points that I don't know how to solve." Is a strong indicator your question will be asking for either; debugging help or for us to implement features. I think you should edit your question to remove this aspect of your question. And instead focus solely on whether the tools you use are on-topic. To not muddy the discussion. Then after this discussion ends you can post your question and the community can VTC if my concern turns out to be true. \$\endgroup\$
    – Peilonrayz Mod
    Jul 10 at 18:23
  • \$\begingroup\$ @Peilonrayz What does VTC mean? \$\endgroup\$
    – igg
    Jul 10 at 18:55
  • 1
    \$\begingroup\$ At 3k reputation users get the Vote To Close (VTC) privilege. The privilege allows users to close off-topic questions. \$\endgroup\$
    – Peilonrayz Mod
    Jul 10 at 19:40
  • \$\begingroup\$ Certain tags not existing does not mean questions about those technologies are unwelcome. However, what is important is that the code works as intended. Does your code produce the correct output? What exactly do you mean with 'pain points'? Whenever wondering whether Code Review is the right place to ask, the help center is a great place to start. If you can answer all 6 questions with 'yes', we can help you further. \$\endgroup\$
    – Mast Mod
    Jul 10 at 20:00
  • \$\begingroup\$ What we don't do, is feature requests. Can you clarify what kind of question you'd be asking? \$\endgroup\$
    – Mast Mod
    Jul 10 at 20:01
  • \$\begingroup\$ Some context: Prometheus, k8s = Kubernetes, Helm, IoT, and DevOps. \$\endgroup\$ Jul 11 at 12:25
  • \$\begingroup\$ "Stack Exchange site", not "stack exchange". See e.g. Proper Use of the Stack Exchange Name. You can edit your question. \$\endgroup\$ Jul 11 at 12:28
  • \$\begingroup\$ @Mast It's difficult to give more details without actually asking the question, hence my initial question here. If I were to summarize my intentions, I would present these things in order: 1) the problem I'm trying to solve 2) my current solution 3) the pain points I have in front of me given the solution I have implemented 4) whether the approach I'm following is at all appropriate 5) whether there are better alternatives. The "code" in this case, would be a collection of yaml files (k8s resource definitions) and how they are applied to the cluster. I hope this helps \$\endgroup\$
    – igg
    Jul 11 at 13:03
  • \$\begingroup\$ I also found out today that there is a DevOps stack exchange, and my question might be more appropriate there. If anyone has any thoughts on that, I'd appreciate those as well \$\endgroup\$
    – igg
    Jul 11 at 13:05
  • \$\begingroup\$ Based on what you've shared with us, I don't have high hopes your question would be suitable for our site. \$\endgroup\$
    – Mast Mod
    Jul 11 at 16:30
  • \$\begingroup\$ I understand, I'll seek other locations. Thank you for your time. \$\endgroup\$
    – igg
    Jul 11 at 16:33


You must log in to answer this question.

Browse other questions tagged .