Skip to content

raise threshold for End2EndIngestionLag #743

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

Merged
merged 1 commit into from
Jun 2, 2023
+4 −4
Merged

raise threshold for End2EndIngestionLag #743

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion charts/posthog/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ type: application

# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
version: 30.22.0
version: 30.22.1

# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application.
Expand Down
6 changes: 3 additions & 3 deletions charts/posthog/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2328,15 +2328,15 @@ prometheus:
needs to be rolled-back.

- alert: End2EndIngestionLag
expr: (max by(scenario) (posthog_celery_observed_ingestion_lag_seconds{scenario=~"ingestion_api|ingestion"})) > 600
expr: (max by(scenario) (posthog_celery_observed_ingestion_lag_seconds{scenario=~"ingestion_api|ingestion"})) > 1200
for: 5m
labels:
rotation: common
severity: critical
annotations:
summary: End-to-end analytics event ingestion lag exceeds 10 minutes for more than 5 minutes.
summary: End-to-end analytics event ingestion lag exceeds 20 minutes for more than 5 minutes.
description: |
Our end-to-end probe measured an ingestion lag higher than 10 minutes for scenario {{ $labels.scenario }}.
Our end-to-end probe measured an ingestion lag higher than 20 minutes for scenario {{ $labels.scenario }}.
Check the "Kafka (cluster overview)" dashboard to identify what topics and partitions are lagging and
follow the https://posthog.com/docs/runbook/services/plugin-server/ingestion-lag runbook for recovery
steps.
Expand Down