このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。
Overview
This integration monitors merge queue length for each configured repository in Mergify and tracks Mergify’s global availability. By sending metrics to your Datadog account, you can set up monitors for anomaly alerts and analyze merge queue performance. You can maintain awareness of Mergify service availability and optimize your development workflow using this Datadog integration.
Setup
- In Datadog: Go to Integrations, select the Mergify tile and click Install Integration.
- Click Connect Accounts to begin authorization of this integration. You will be redirected to the Mergify dashboard.
- In the Mergify dashboard: Log in, select the organization you would like to set up the Datadog Integration for and click Connect the integration.
Your Mergify statistics now appear in Datadog.
Uninstallation
- Go to the Mergify dashboard, log in, and navigate to Integrations.
- Click the Disconnect button in the Datadog tile.
Once this integration has been uninstalled, any previous authorizations are revoked.
Note: Ensure that all API keys associated with this integration have been disabled by searching for the integration name on the Datadog API Keys page.
Data Collected
Metrics
mergify.merge_queue_length (gauge) | Merge queue length |
mergify.time_to_merge.median (gauge) | Median time to merge Shown as second |
mergify.time_to_merge.mean (gauge) | Mean time to merge Shown as second |
mergify.queue_checks_outcome (gauge) | Number of outcomes for the queue operation. Each outcome type can be found in the tag 'outcome_type' |
mergify.queue_freeze.duration (gauge) | Merge queue freeze duration Shown as second |
For the metric mergify.queue_checks_outcome
, the available outcome_type
tags are :
PR_DEQUEUED
: The number of PRs that have been manually removed from the queuePR_AHEAD_DEQUEUED
: The number of PRs that have been removed from the queue because a PR ahead of it was removed from the queuePR_AHEAD_FAILED_TO_MERGE
: The number of PRs that have been removed from the queue because a PR ahead of it failed to mergePR_WITH_HIGHER_PRIORITY_QUEUED
: The number of PRs that have been removed from the queue because a PR with higher priority has been queuedPR_QUEUED_TWICE
: The number of PRs that have been removed from the queue because they have been queued twiceSPECULATIVE_CHECK_NUMBER_REDUCED
: The number of PRs that have been removed from the queue because the number of speculative checks in the config was changedCHECKS_TIMEOUT
: The number of PRs that have been removed from the queue because the speculative checks have timed outCHECKS_FAILED
: The number of PRs that have been removed from the queue because the speculative checks have failedQUEUE_RULE_MISSING
: The number of PRs that have been removed from the queue because the queue rule that was used to queue the PR has been removed from the configUNEXPECTED_QUEUE_CHANGE
: The number of PRs that have been removed from the queue because a user made an operation on the queued pull requestPR_FROZEN_NO_CASCADING
: The number of PRs that have been removed from the queue because they were frozen by a freeze with no cascading effectTARGET_BRANCH_CHANGED
: The number of PRs that have been removed from the queue because the PR’s target branch was changedTARGET_BRANCH_MISSING
: The number of PRs that have been removed from the queue because the PR’s target branch does not exist anymorePR_UNEXPECTEDLY_FAILED_TO_MERGE
: The number of PRs that have been removed from the queue because they unexpectedly failed to get mergedBATCH_MAX_FAILURE_RESOLUTION_ATTEMPTS
: The number of PRs that have been removed from the queue because the maximum batch failure resolution attempts have been reached
Service Checks
Mergify does not include any service checks.
Events
Mergify does not include any events.
Support
Need help? Contact Mergify support.