Introduction

Jenkins is a tool that helps automate tasks like building and testing software. Monitoring Jenkins health means checking if Jenkins is running well and ready to do its job without problems.

When you want to know if Jenkins is up and running after a restart or update

When you need to check if Jenkins has enough resources like memory and disk space

When you want to see if Jenkins jobs are running smoothly without errors

When you want to get alerts if Jenkins becomes slow or unresponsive

When you want to track Jenkins system logs to find issues early

Commands

This command checks if the Jenkins web interface is reachable and responding by requesting the login page.

Terminal

curl -s http://localhost:8080/login

Expected OutputExpected

<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <title>Jenkins</title> </head> <body>  </body> </html>

→

-s - Runs curl silently without progress meter

This command shows the current status of the Jenkins service on the server, telling if it is active and running.

Terminal

systemctl status jenkins

Expected OutputExpected

● jenkins.service - Jenkins Continuous Integration Server Loaded: loaded (/lib/systemd/system/jenkins.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2024-06-14 10:00:00 UTC; 1h 30min ago Main PID: 1234 (java) Tasks: 35 (limit: 4915) Memory: 512.0M CGroup: /system.slice/jenkins.service └─1234 /usr/bin/java -jar /usr/share/jenkins/jenkins.war

This command checks the disk space usage of the Jenkins home directory to ensure there is enough free space for builds and logs.

Terminal

df -h /var/lib/jenkins

Expected OutputExpected

Filesystem Size Used Avail Use% Mounted on /dev/sda1 100G 40G 60G 40% /var/lib/jenkins

→

-h - Shows sizes in human-readable format

This command shows Jenkins service logs from the last hour to help find any recent errors or warnings.

Terminal

journalctl -u jenkins --since "1 hour ago" --no-pager

Expected OutputExpected

Jun 14 10:05:00 myserver systemd[1]: Started Jenkins Continuous Integration Server. Jun 14 10:10:00 myserver jenkins[1234]: INFO: Jenkins is fully up and running Jun 14 10:30:00 myserver jenkins[1234]: WARNING: Disk space low on /var/lib/jenkins

→

--since "1 hour ago" - Shows logs from the last hour

→

--no-pager - Shows all logs without paging

Key Concept

If you remember nothing else from this pattern, remember: regularly check Jenkins service status, web response, disk space, and logs to keep Jenkins healthy.

Common Mistakes

Trying to access Jenkins web interface without Jenkins running

The web page will not load because the Jenkins service is stopped

First check Jenkins service status with 'systemctl status jenkins' and start it if needed

Ignoring disk space warnings on Jenkins home directory

Builds and logs can fail or cause Jenkins to crash if disk space runs out

Regularly check disk space with 'df -h /var/lib/jenkins' and clean up if low

Not checking Jenkins logs for errors

Problems may go unnoticed until they cause failures

Use 'journalctl -u jenkins' to review recent logs and catch issues early

Summary

Use 'curl' to verify Jenkins web interface is responding.

Check Jenkins service status with 'systemctl status jenkins'.

Monitor disk space on Jenkins home directory using 'df -h'.

Review Jenkins logs with 'journalctl' to detect errors or warnings.