OpenObserve + Twenty CRM: Sustained Capacity Review Tasks

Stay ahead of sustained capacity pressure with OpenObserve + Twenty CRM review tasks

This n8n workflow automatically checks Prometheus-style infrastructure metrics in OpenObserve, detects sustained breach/capacity pressure, and then creates or updates matching review tasks in Twenty CRM with clear evidence from the latest and previous time windows.

What this workflow does

• Runs on demand or on a schedule: use a manual trigger for preview, or run every 30 minutes via a scheduled trigger.
• Applies a capacity policy: configures PromQL, time window, step, threshold, coverage, and sustained-breach rules, then validates the policy and calculates aligned start/end timestamps.
• Queries OpenObserve with a Prometheus range query across the computed time range to retrieve the metric history.
• Classifies each time series by evaluating:
  • data freshness/coverage
  • breach duration and breach fraction
  • trend vs the previous window
  Categories include healthy, transient pressure, sustained pressure, insufficient data, or no data.
• Creates/updates Twenty CRM tasks with evidence: builds a stable task title and a Markdown evidence block (labels, threshold stats, and the PromQL used). For sustained-pressure series, it either updates an existing task (replacing only the marked evidence block) or creates a new one when preview mode is disabled.
• Outputs a consolidated run report showing created/updated/preview/skipped outcomes.

Use cases

• Auto-generate capacity review tasks when CPU, memory, or other infrastructure signals show sustained pressure.
• Reduce false alarms by requiring coverage and sustained-breach criteria before triggering Twenty CRM follow-ups.
• Provide operators with consistent, query-backed evidence to speed up incident reviews and capacity planning.

Technical details

• Integrations/Credentials: OpenObserve API credential + Twenty CRM API credential.
• n8n nodes/logic mentioned in the workflow: manual trigger, if, set, code, sticky note, and split in batches.
• Uses PromQL to perform OpenObserve Prometheus range queries and enforces sustained-breach and coverage rules.