AppsPricingBlogTry it
Datadog logo
GitLab logo

Connect Datadog to GitLab

Use 1 documented Datadog triggers to run 15 documented GitLab actions.

1 source triggers
15 target actions
Reverse direction supported

Why Connect Datadog & GitLab?

Start with a Datadog event

Choose from 1 documented triggers, including New Monitor Event (Instant).

Run a GitLab action

Send the event into one of 15 documented actions, such as Create Branch, Create Epic, Create issue.

Map and review the workflow

Choose the fields and conditions for the workflow, then test the result before activation.

Available Triggers & Actions

Datadog logo

Datadog

Triggers (1)

New Monitor Event (Instant)

Emit new events captured by a Datadog monitor

webhook

Actions (13)

Get Account Info

Detect the Datadog region for the connected account. Call this FIRST before any other Datadog tool if you do not already know the region. Returns the region domain (e.g. datadoghq.com) which must be passed as the region parameter to **Search Logs**, **Search Monitors**, **Get Metric Data**, and all other Datadog tools. See the docs

Get Account Region

Detect the Datadog region for the connected account by validating the API key against each regional endpoint. Use this to discover the correct region before calling other Datadog actions. See the docs

Get Metric Data

Query time-series metric data for analyzing trends and system performance. Query syntax: avg:system.cpu.user{*}, sum:requests.count{env:prod} by {host}, max:system.mem.used{service:web}. Both from and to are POSIX timestamps in seconds. Use **Search Metrics** first to discover available metric names. Use **Search Hosts** to find valid host tags for scoping. After finding anomalies, use **Search Logs** to investigate related entries. See the docs

List Logs

Get a list of logs matching a filter query. Uses the GET endpoint with a higher rate limit (3600/hr vs 300/hr). See the docs

Post Metric Data

Post custom time-series metric data points to Datadog. Data appears in dashboards, monitors, and can be queried via **Get Metric Data**. Points: JSON object where keys are Unix timestamps (seconds) and values are numeric, e.g. {"1640995200": 1.0}. Use **Search Metrics** to verify a metric name exists, or post to a new name to create it. This is a WRITE operation that creates or appends data to a metric time series. See the docs

Search Dashboards

List and search Datadog dashboards. Returns dashboard IDs, titles, URLs, and metadata. Dashboard URL: https://app.{region}/dashboard/{id} where region comes from **Get Account Info**. Use alongside **Search Services** to find dashboards related to a specific service. See the docs

Search Events

Search Datadog events: monitor state changes, deployment markers, error spikes, and infrastructure events. Filter by sources (e.g. nagios,docker), tags (e.g. env:prod,service:web), and priority (normal or low). Time range defaults to last 24h (POSIX timestamps in seconds). To investigate a monitor alert, use **Search Monitors** first, then search events for the relevant time range. Follow up with **Search Logs** for deeper investigation. See the docs

Search Hosts

Search monitored infrastructure hosts. Filter by tag (env:production), name (host:web-01), or partial match. Sort by cpu, iowait, load, status, or apps. Host names from results can scope queries in **Get Metric Data** (e.g. avg:system.cpu.user{host:web-01}), filter logs in **Search Logs** (host:web-01), or filter metrics in **Search Metrics**. Max 1000 results. See the docs

Search Incidents

Search Datadog incidents by state, severity, and metadata. Query syntax: state:active, state:resolved, severity:SEV-1. After finding an incident, investigate with: **Search Logs** for the incident time window, **Get Metric Data** for relevant metrics, **Search Events** for related monitor alerts, and **Search Services** for ownership info. See the docs

Search Logs

Search Datadog logs matching a query with support for facets and time ranges. Uses log search syntax: service:web-app status:error, @http.status_code:>=400, boolean operators (AND, OR, NOT), and wildcards. Set from to now-1h for recent logs. Use **Search Metrics** to discover metric names or **Search Hosts** to find host names for filtering. To investigate an incident, use **Search Incidents** first, then search logs for that time window and service. See the docs

Search Metrics

Discovery tool: list available Datadog metric names, optionally filtered by host. Returns metric name strings (e.g. system.cpu.user, aws.ec2.cpuutilization) for use in **Get Metric Data** queries with the syntax aggregation:metric.name{tags}. Use **Search Hosts** to find valid host names for the host filter. See the docs

Search Monitors

Search Datadog monitors (alerting rules) including status, thresholds, and conditions. Query syntax: tag:env:production, type:metric, status:Alert. Tags filter: comma-separated (e.g. env:prod,team:backend). After finding a monitor, use **Search Events** to see recent state changes, or **Get Metric Data** to query the underlying metric it tracks. Returns monitor ID, name, type, query, status, and tags. See the docs

Search Services

List services from Datadog's Service Catalog with ownership, metadata, and team info. Use to discover service names for filtering in **Search Logs** (service:my-app) or finding monitors via **Search Monitors** (tag:service:my-app). Returns service definitions including links, docs, and on-call. See the docs

GitLab logo

GitLab

Triggers (10)

New Commit (Instant)

Emit new event when a new commit is pushed to a branch

webhook
New Branch (Instant)

Emit new event when a new branch is created

webhook
New Project

Emit new event when a project (i.e. repository) is created

polling
New Audit Event (Instant)

Emit new event when a new audit event is created

webhook
New Commit Comment (Instant)

Emit new event when a commit receives a comment

webhook
New Issue (Instant)

Emit new event when an issue is created in a project

webhook
New Mention (Instant)

Emit new event when you are @mentioned in a new commit, comment, issue or pull request

webhook
New Merge Request (Instant)

Emit new event when a merge request is created

webhook
New Milestone

Emit new event when a milestone is created in a project

polling
New Review Request (Instant)

Emit new event when a reviewer is added to a merge request

webhook

Actions (15)

Create Branch

Create a new branch in the repository. See the documentation

Create Epic

Creates a new epic. See the documentation

Create issue

Creates a new issue. See the documentation

Get Issue

Gets a single issue from repository. See the documentation

Get Repo Branch

Get a single project repository branch. See the documentation

List Commits

List commits in a repository branch. See the documentation

List Group ID Options

Retrieves available options for the Group ID field.

List Group Path Options

Retrieves available options for the Group Path field.

List Groups

List all groups. See the documentation

List Project ID Options

Retrieves available options for the Project ID field.

List Project Members

List all members of a project. See the documentation

List Repo Branches

Get a list of repository branches from a project. See the documentation

Search Issues

Search for issues in a repository with a query. See the documentation

Update Epic

Updates an epic. See the documentation

Update Issue

Updates an existing project issue. See the documentation

Integration Features

1 documented Datadog triggers
15 documented GitLab actions
Configurable field mapping
Conditional workflow steps
Execution monitoring
A supported GitLab to Datadog direction

Capability Examples

Datadog trigger → GitLab action

Catalog example
DatadogDatadog

New Monitor Event (Instant)

GitLabGitLab

Create Branch

GitLab trigger → Datadog action

Reverse direction
GitLabGitLab

New Commit (Instant)

DatadogDatadog

Get Account Info

How It Works

1

Connect Apps

Authenticate your Datadog and GitLab accounts

2

Choose a Trigger

Select a documented Datadog event

3

Choose an Action

Select the documented GitLab operation to run

Test and Review

Verify field mapping and provider responses before activation

Frequently Asked Questions

Integration Benefits

Trigger-driven Workflows

Start the supported direction from one of 1 documented Datadog triggers.

Automated Actions

Run one of 15 documented GitLab actions after the selected trigger fires.

Provider Authentication

Review the authentication requirements published by each provider before activating the workflow.

Guided Configuration

Select a documented trigger, choose a target action, and map the fields required by the workflow.

Field Mapping

Map the fields exposed by the selected trigger and action, then review the required provider inputs.

Execution Review

Test the workflow and review provider responses before relying on it in production.

GitLab logoDatadog logo

Reverse Integration Available

Also connect GitLab to Datadog for bidirectional automation

View Integration
Datadog logo

All Datadog Integrations

Explore all available Datadog connections

View All Integrations
GitLab logo

All GitLab Integrations

Explore all available GitLab connections

View All Integrations

Ready to Connect Datadog & GitLab?

Build this supported workflow in Mazaal AI and test it with your own provider accounts.

Get Started Free