Skip to content

GKGPipelinePostCompileErrorRateHigh

Post-compile failure rate is above 1%, isolating server-side reliability from client-input quality. Severity s3, fires after 5m.

The failure rate of queries that passed compilation exceeds 1%. Excluding compile_error filters out bad client input, so what remains (execution, authorization, security, internal) is the server’s own reliability. This mirrors the “Pipeline success rate (1h), post-compile” gauge on the overview dashboard. When GKGQueryingErrorRateHigh fires but this one does not, the problem is client input, not the service.

The firing expression, on gkg_query_pipeline_queries_total (emitted by the service, see the metrics catalog):

sum by (env, environment, stage) (rate(gkg_query_pipeline_queries_total{status!~"ok|compile_error"}[5m]))
/ sum by (env, environment, stage) (rate(gkg_query_pipeline_queries_total{status!="compile_error"}[5m])) > 0.01
  • Silence via Alertmanager filtered on the alertname.
  • Fires without GKGQueryingErrorRateHigh when the server is failing but total volume dilutes the aggregate rate.
  • s3, no paging. Excludes client input errors, so this is server-side reliability degrading.
sum by (status) (rate(gkg_query_pipeline_queries_total{status!~"ok|compile_error"}[5m]))
  • execution: ClickHouse failing queries, cross-check GKGExecutionFailureRate.
  • authorization: the Rails redaction/authorization exchange failing, cross-check GKGAuthorizationFailureRate.
  • security: cross-check GKGSecurityRejected.
SymptomCauseAction
execution dominatesClickHouse failing queriesFollow GKGExecutionFailureRate
authorization dominatesRails redaction exchange failingFollow GKGAuthorizationFailureRate
No single mode dominates, rose with a deployRelease regressionRoll back the image tag and investigate offline

Follow the dominant failure mode’s own playbook (linked above). If no single mode dominates and the rate rose with a deploy, roll back the image tag and investigate offline.

  • Graph ClickHouse (ClickHouse Cloud)
  • GitLab Rails (JWT minting, internal Orbit API)

Ask in #f_orbit_dev (context_systems).

  • Alert rule (hand-maintained; keep the expr above in sync when tuning it).