Disabling probe

[Pagehey]

Hello 👋

First, thanks for this gem, it fits perfectly my needs 🙏

I am a bit confused about the probe check feature.

I just realised that the every minute ping on "/" from 127.0.0.1 that I was desperatly looking for the source was not from my hosting service but from GoodJob's healt check probe.

My problem is that it's actually calling the root page of my app, and thus is flooding log and montoring. I don't think it's the expected behavior, is it?

It's may be a dumb question, but could you please explain simply what's the purpose of that probe.
Can it be disabled (if it's not a bad idea)?

From the README I understand the the probe is useful for containerized environnement, which is not my case, so why is the probe active an calling my home page? I tried to understand its behavior from the merge requests linked to it, but I still can't figure out how it's supposed to work 😓

Thanks for the help.

If something is not clear, please tell me, I wasn't sure how to explain my problem 😅

[bensheldon]

That's weird that you're seeing a ping coming from something GoodJob related. GoodJob's probe feature exposes an http endpoint for healthcheck probes; nothing in GoodJob would make an http request.

The expected usage of the feature is that something in your platform/container environment would make an http request to the GoodJob service to detect readiness/liveness.

I imagine this is either:

• You have platform healthcheck configured, but it's aimed at the wrong service
• You have something (a job, some GoodJob configuration value that your app has made lambda/proc) that is making that web request

[Pagehey]

Oh I'm so sorry, you're right, the ping does not come from GoodJob. I was misled by my server's logs, I thought the ping stopped the moment I stopped GoodJob but it was a "fake positive".
It must surely be one of the two options you mentioned, but I'm in the fog again! 😶‍🌫️

Thank you and sorry again for this issue that is not one! 🙏 I'm closing it right away