> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # GitLab on Vortex IQ > Monitor GitLab health, cost and reliability signals, and catch incidents and runaway spend early. Monitor GitLab health, cost and reliability signals, and catch incidents and runaway spend early. [Connect or manage this source](https://app.vortexiq.ai/workbench/settings/sources) · [How connecting works](/integrations/connector-catalogue) · [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=gitlab) performance signals automated checks prepared fixes proven workflows API operations ### What you can achieve Capabilities are grouped around merchant outcomes, not API terminology. Improve discovery, conversion, campaigns and repeat purchase. Monitor orders, fulfilment, delivery and settlement. Find failures, leaks and risks before they cost sales. ### From connection to verified outcome The controlled sequence every capability follows. Nothing changes a connected system without the approval step. Authorise the source. Scopes are shown before access is granted. Watch the signals against your own baselines, not universal defaults. Run checks and gather evidence specific to your store. Explain what happened, why it matters and the proposed action. You review scope, risk and reversibility before anything changes. Apply through governed connector operations. Confirm the intended result and keep the receipt. No changes are made without the configured approval policy. Read-only operations do not modify the connected system; schedules, access scopes, API usage and data handling remain governed by Vortex IQ controls. ### Monitor performance 21 performance signals. Open an outcome to see its signals and how each one alerts. Read-only operations do not modify the connected system. | Signal | Alert behaviour | What it tracks | | -------------------------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------ | | **Active Projects (30d)** | Watch only | Count of projects with last\_activity\_at within the last 30d and archived=false. | | **Avg Commits / Active Project (30d)** | Watch only | 30d commit count / active-projects-30d; concentration of delivery across the fleet. | | **Daily Commits Trend** | Watch only | Commits grouped by day over the last 30d (created\_at), summed across the top 10 projects. | | **MR Age Alert** | Alert band 3 / 14 | Median open-MR age in days; fires when it crosses the vc\_pr\_age\_days band (bad at >14d). | | **Median Open MR Age** | Alert band 3 / 14 | Median of (now - created\_at) in days across all open MRs; drives vc\_pr\_age\_days (lower is better). | | **Merged MRs (30d)** | Watch only | Count of MRs with merged\_at within the last 30d (state=merged\&order\_by=updated\_at) across the top 10 projects. | | **Most Active Project (30d)** | Watch only | The project with the most commits in the last 30d; value = commit count, detail = path\_with\_namespace. | | **Open Issues** | Watch only | Sum of open\_issues\_count across all projects returned by /projects. | | **Open Merge Requests** | Watch only | Count of open MRs from /projects/{id}/merge\_requests?state=opened across the top 10 projects. | | **Pipelines Run (30d)** | Watch only | Count of pipelines created within the last 30d across the top 10 projects. | | **Projects** | Watch only | Count of projects returned by /projects (membership=true). | | **Stale MRs (>14d)** | Watch only | Count of open MRs whose age (now - created\_at) exceeds 14 days. | | **Total Stars** | Watch only | Sum of star\_count across all projects. | | Signal | Alert behaviour | What it tracks | | -------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Commits (30d)** | Alert band 0 / -50 | Count of commits from /projects/{id}/repository/commits (created\_at within 30d) summed across the top 10 projects; change\_pct vs the prior 30d drives | | **Deploy Cadence Trend** | Alert band 0 / -50 | Daily count of commits over 30d; value = 30d total, change\_pct vs the prior 30d drives vc\_deploy\_cadence. | | **Deploy Stall Alert** | Alert band 0 / -50 | Commit-count change\_pct vs the prior 30d; fires on a stall per the vc\_deploy\_cadence band. | | **Pipeline Health Score** | Alert band 90 / 70 | 0-100 composite = 0.4 x pipeline success rate + 0.3 x MR-age score (100 at \<=3d, 0 at >=14d) + 0.3 x deploy-cadence score (100 + cadence change\_ | | **Projects by Visibility** | Watch only | Projects grouped by the visibility field (private, internal, public). | | Signal | Alert behaviour | What it tracks | | ------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------- | | **Failed Pipelines (30d)** | Watch only | Count of pipelines with status=failed created within the last 30d across the top 10 projects. | | **Pipeline Success Rate (30d)** | Alert band 95 / 80 | Pipelines with status=success / all completed pipelines (status in success, failed, canceled) created within 30d, x100, across the top 10 projects. | | **Pipelines by Status (30d)** | Watch only | Pipelines created within the last 30d grouped by status field (success, failed, canceled, skipped, etc.) across the top 10 projects. | ### Audit risks and opportunities A fix status appears only where the action, inputs, approval, verification and recovery controls are mapped. Candidate remediations are never executable. Open a check for the detail. **Severity** high · **Outcome** Run operations · **Fix status** Report only More than 1 in 5 CI runs is failing. At this rate, a genuinely broken change is more likely to slip through unnoticed (lost in the normal noise of failures) and developers waste time re-running or diagnosing failures that have nothing to do with their own change, slowing the whole team down. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `VC-CI-001` **Severity** medium · **Outcome** Grow revenue · **Fix status** Report only Deploys or merges have dropped by more than half compared to the prior period. That usually means fixes and improvements, including fixes for issues this same audit has flagged elsewhere, are not shipping, which slows the whole team's ability to respond to anything urgent. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `VC-CADENCE-001` **Severity** medium · **Outcome** Run operations · **Fix status** Report only Half of open pull requests have been waiting more than two weeks. Work that is done but not merged is not delivering any value yet, and the longer a PR sits open, the more it tends to drift from the main branch, making it harder to merge later than it would have been today. Vortex IQ detects and explains this; resolution is manual, with evidence and recommended steps. Reference: `VC-PR-001` #### Build your own automated fixes Turn any finding into an automated fix with a Vortex IQ workflow: **over 13,000 read and write operations across more than 200 connectors** are available as building blocks, with approval, verification and rollback on every change. ### Automate approved work Vortex IQ is integrated with **5 read** and **0 write** operations across projects, projectmergerequests, projectpipelines, projectrepositorycommits, users on GitLab. Combine them with anything from the **over 13,000 operations across more than 200 connectors** to automate the work in your own words. Changes follow your configured approval policy: the target, proposed change, affected records, risk, reversibility and verification plan are shown before execution. [Create a workflow](https://app.vortexiq.ai/workbench/flows/create?connector=gitlab) #### Ready to build your first GitLab workflow Pick a trigger, add the operations above as steps, and every step that changes data pauses for your approval. Monitoring and audits are live now and can start any workflow you build. | Resource | Read operations | Write operations | | ------------------------ | --------------- | ---------------- | | projects | 1 | 0 | | projectmergerequests | 1 | 0 | | projectpipelines | 1 | 0 | | projectrepositorycommits | 1 | 0 | | users | 1 | 0 | Signed-in users see the full catalogue in the workflow builder, filtered to the sources they have connected.