Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: use prom to measure celery queue depth #17682

Merged
merged 1 commit into from
Sep 29, 2023
Merged

chore: use prom to measure celery queue depth #17682

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions posthog/celery.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,11 @@
labelnames=["task_name"],
)

CELERY_TASK_QUEUE_DEPTH_GAUGE = Gauge(
"posthog_celery_queue_depth",
"We use this to monitor the depth of the celery queue.",
)

# Using a string here means the worker doesn't have to serialize
# the configuration object to child processes.
# - namespace='CELERY' means all celery-related configuration keys
Expand Down Expand Up @@ -684,6 +689,9 @@ def redis_celery_queue_depth():

try:
llen = get_client().llen("celery")
CELERY_TASK_QUEUE_DEPTH_GAUGE.set(llen)

# TODO this can be removed once we're using the prom metric for alerting
with pushed_metrics_registry("celery_redis_queue_depth") as registry:
depth_gauge = Gauge(
"posthog_celery_queue_depth",
Expand Down