Uptime monitors with interval > 300 not executed
Review this checklist before submitting.
-
GitLab issues are for bug reports and feature requests. If this is a help request, post on Gitter. If you have or want paid support, please use the chat widget on https://glitchtip.com. -
Document reproduction steps. Be as detailed as possible. -
If applicable, try to reproduce the problem on https://app.glitchtip.com -
Be considerate of the reviewer of your issue and their time. They are likely unpaid. GlitchTip is open source and comes with absolutely no warranty. -
Check existing issues first. 👍 the issue to show interest. -
Do not open issue related to automated security scanners or other static anaysis tool. We use Renovate and GitLab for this. Instead, ask on Gitter how you can help get involved in the project and make the changes you wish to see.
Description
I have created some uptime monitors, most of them had an interval of 600 (10min). With the update to 3.4.6 (from pre 3 version), only monitors with intervals lower than 300 or so (still investigating) are regularly checked. Those with 600 are checked once, after updating the monitor, but never again after that.
I've checked my celery log, and there are monitor dispatch and another task, that are regularly executing. As I can see, there is Redis used, is that true? I thought this was not an explicit dependency, at least not when I was helping with https://glitchtip.com/documentation/install#installing-without-docker - so, my question besides help with this issue is: Is Redis needed to run glitchtip?
As I am self hosting, here is my celery command:
celery --app glitchtip worker --beat --schedule ./celerybeat-schedule --loglevel INFO --concurrency 1 --max-tasks-per-child 50 --max-memory-per-child=300000
Proposed Solution(s)
I could document things in the installation manual.