*Hi all,*
I’ve extended our GATUS <https://github.com/TwiN/gatus>-based health check app to also monitor pipelines using cron schedules. Each endpoint is configured as either: - *Regular* → polled at fixed intervals (e.g., every 1 minute) - *Job-based* → triggered based on a cron expression ------------------------------ *Problem:* In *STAGING*, some job-type endpoints are being triggered *both* by cron *and* at the 1-minute interval, even though they should only run via cron. This started happening unexpectedly one day, despite working fine initially. This issue *does not occur in DEV*. ------------------------------ *Deployment Context:* - *DEV*: Single AKS pod, ~40 endpoints – no issues - *STAGING*: 6 AKS pods, ~1000 endpoints – duplicate monitoring observed ------------------------------ *What I’ve Checked:* - Logs confirm each endpoint is following the correct logic path at runtime - I scaled up the dev environment to 6 pods to replicate the issue, but it did not occur there. I then scaled down the pods in staging, but the issue continued. - Refactored the code with minor optimisations -> pushed to staging and still, issue persisted. ------------------------------ *Code:* https://www.sharecode.in/QGlCYj ------------------------------ *Question:* Could someone please review the code and let me know if there’s anything that could be causing this issue—particularly in a multi-pod environment or is there something else? Thanks in advance! -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/3bd29ffb-fdd8-4db6-989c-fbb03057813cn%40googlegroups.com.
