Closed WillNilges closed 1 month ago
Attention: Patch coverage is 85.71429%
with 4 lines
in your changes missing coverage. Please review.
Project coverage is 95.02%. Comparing base (
4e72638
) to head (6277ec8
).
Files | Patch % | Lines |
---|---|---|
src/meshdb/celery.py | 85.71% | 4 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Happy to override codecov here. Testing celery statically is hard. With Datadog will we be able to monitor to ensure the tasks are running and alert if they stop? (and can we document that requirement, in #88 perhaps)
Can we move these celery related scripts into sub-directories? It's a lot of clutter for the root of the repo
Perhaps:
bin/
celery/
All the celery stuff
All the other scripts we're collecting
@Andrew-Dickinson I agree. I was going to make a scripts/
directory in a follow-up PR, but I'm happy to do it in this one.
Happy to override codecov here. Testing celery statically is hard. With Datadog will we be able to monitor to ensure the tasks are running and alert if they stop? (and can we document that requirement, in #88 perhaps)
Certainly. Feel free to add that to the reqs.
~maybe we can get the redefinitions to stop if we break out the checks into other files, like in the blog post I attached in the description.~
Update: Tried it, no dice.
Moves celery out of the main meshdb pod and into its own. The beat and worker each get their own container within that pod, and everyone communicates through Redis.
Inspired by: https://medium.com/ambient-innovation/health-checks-for-celery-in-kubernetes-cf3274a3e106