Jenkins
Receive build notifications and log deployments as changes to correlate with incidents.
Quick Setup
Copy Webhook URL
Go to your Alert24 dashboard and copy the webhook URL for Jenkins.
Configure Jenkins
Add the webhook URL in your Jenkins settings.
Auto-Detected
Alert24 auto-detects Jenkins payloads and maps them to incidents.
Step-by-Step Setup Instructions
Jenkins Webhook Setup
post {
failure {
httpRequest url: '<WEBHOOK_URL>',
httpMode: 'POST',
contentType: 'APPLICATION_JSON',
requestBody: '{"build": {"status": "FAILURE", "full_url": "${BUILD_URL}"}}'
}
}Example Webhook Payload
This is a sample payload that Jenkins sends to Alert24 when an alert fires.
{
"build": {
"status": "FAILURE",
"full_url": "https://jenkins.example.com/job/deploy/42/",
"number": 42,
"phase": "COMPLETED"
},
"name": "deploy-production"
}How Alert24 Maps Jenkins Data
Status Field
build.status
Message Field
build.full_url
Auto-Create Incidents
Yes
Auto-Resolve Incidents
Yes
Status Mapping
| Alert24 Status | Jenkins Values |
|---|---|
| operational | SUCCESS |
| degraded | UNSTABLE |
| down | FAILUREABORTED |
Track Deployments from Jenkins
Track changes for incident correlation and AI root cause analysis
- 1Add your Alert24 Changes Webhook URL as a Jenkins credential
- 2Add a post-build step or pipeline stage that sends a POST request
// Jenkinsfile
post {
success {
sh """
curl -s -X POST "${ALERT24_CHANGES_URL}" \\
-H "Content-Type: application/json" \\
-d '{
"summary": "Jenkins build #${BUILD_NUMBER}",
"change_type": "deployment",
"commit_sha": "${GIT_COMMIT}",
"branch": "${GIT_BRANCH}",
"changed_by": "${BUILD_USER}"
}'
"""
}
}Changes are logged per service. Copy the Changes Webhook URL from your service page in Alert24. When an incident occurs, recent changes are surfaced automatically with AI-powered root cause analysis. Learn more →
Connect Jenkins to Alert24 in minutes
Free plan includes 5 monitors, 1 status page, and incident management. No credit card required.
More CI/CD & DevOps Integrations
GitHub
InboundLog pull request merges, pushes, and releases as changes for incident correlation.
GitHub Actions
InboundReceive workflow run notifications and log deployments as changes to correlate with incidents.
GitLab CI
InboundReceive pipeline notifications and log deployments as changes to correlate with incidents.
CircleCI
InboundReceive job notifications and log deployments as changes to correlate with incidents.
Terraform Cloud
InboundReceive run notifications and log infrastructure changes to correlate with incidents.
Azure DevOps
InboundReceive pipeline and release notifications and log deployments as changes for incident correlation.