Documentation
Deployment Intelligence
Every deployment is an observed change event from CI/CD or the API. Mydle never invents history. Correlations to monitors, browser, logs, traces, alerts, and incidents are labeled Observed / Likely / Unknown — never causation.
Deployment sources
Connect GitHub Actions, GitLab CI, Vercel, Railway, Docker, and generic webhooks (Bitbucket, Azure DevOps, Jenkins, CircleCI, Render, and others). Each source uses a webhook URL under /api/deployments/hooks/{provider} and the workspace-shared DEPLOYMENTS_HOOK_SECRET.
Open Connected sources in the product for copy-paste URLs and the webhook tester.
Webhook API
POST JSON to a provider hook with headers:
x-mydle-workspace-id— target workspacex-mydle-hook-secret— must matchDEPLOYMENTS_HOOK_SECRET- Optional
x-mydle-dry-run: 1— validate and normalize only; never stores an event
Programmatic ingest also exists on the versioned API (/api/v1/deployments) with an API key. Idempotent on provider + externalId.
GitHub Actions
Send your workflow deployment conclusion to /api/deployments/hooks/github_actions. Normalized fields include status, SHA, branch, environment, and author when present in the payload. If a field is missing, the UI shows em dashes — never fabricates commits.
GitLab CI
Use /api/deployments/hooks/gitlab_ci with a deployment or job payload. Same header auth as other providers.
Generic webhook
Providers without a dedicated normalizer use generic_webhook. Minimum body includes a title (and ideally status, version, gitSha, externalId). Validate with dry-run before enabling live ingest.
Rollback
When a provider marks a deploy as rollback (isRollback or status rolled_back), the release page shows previous deployment linkage and post-window evidence. Recovered alerts or latency improvements appear only if observed after the rollback — otherwise Unknown.
Release correlation
Detail pages soft-compose Related Resources: browser sessions, logs, traces, alerts, incidents, API requests, and audit events in the project / post-deploy window when IDs or time links exist. Empty sections stay hidden. Relationship Graph accepts ?deploymentId=.
Release health
After a deploy, health checks derive from linked monitors (via open alerts in-window), browser session errors, trace error rates, incidents, and alerts. Pass / fail / unknown only — no composite score.
Architecture
Compose-only on existing Monitoring, Browser, Logs, Tracing, Incidents, Alerts, AI, Billing, and Auth engines. Storage lives in deployment tables; overview and detail UIs are thin composers. See docs/architecture/deployments.md in the repository for the canonical model.