The slides are part of a webcast we delivered, where we discussed about the following issues: -- Why monitoring is important? -- The monitoring challenges -- Which components you should monitor on Jenkins -- What metrics you should be tracking on Jenkins -- Introducing ALM Vitality tool -- Q&A ALM Vitality monitors many of your Jenkins components and IT resources and alerts you when a service or component has stopped functioning, giving you key information and helping you get a root cause analysis immediately. To learn more and download: http://almtoolbox.com/jenkins-monitoring Webcast is available here: https://www.youtube.com/watch?v=U0OvAGzGw-Y

1. Monitoring your Jenkins
Deployment
almtoolbox.comTamir Gefen
ALMtoolbox CEO
David Cohen
Product Manager

2. 2
Selected Customers

3. Agenda
 Why monitoring?
 The monitoring challenges
 Which components you should monitor on Jenkins
 What metrics you should be tracking on Jenkins
 Introducing ALM Vitality
 Q&A

4. Monitoring: Why?

5. Monitoring: Why?
 Verify 100% working system
 Gain better control over the system
 Identify problems when they small
 Identify resources bottlenecks
 Get root cause reasons
 Single source of truth
 The base for making decisions
 DevOps best practices…

6. The Monitoring Challenges
1. Defining what components and metrics to monitor
2. Lack of time or knowledge (or both…)
3. End-user interface (UI)
4. Scalable system
5. Customizable and flexible system
6. Consolidate both IT and application
data

7. Jenkins Components
 Physical virtual hosts
 Masters slaves
 Queues, executors, jobs
 IT resources (Memory, CPU,
network, storage etc.)
 Web application
 JAVA (JVM)
 etc…

8. Metrics and KPIs
 Application: queues, executors, jobs
 IT resources (memory, CPU, storage etc.)

9. Introducing ALM Vitality

10. Components and Metrics to Track
1. Stuck jobs and dependencies
2. Jenkins web application
3. Java virtual machine
Application Side:
Jenkins Logo CC-BY-SA 3.0 Made by Jenkins Project
http://jenkins-ci.org

11. Settings Application

12. Application Side:
Stuck Jobs Notification

13. Email Notifications

14. Components and Metrics to Track (2)
4. Host alive
5. Jenkins service process
6. Port is listening
7. Storage capacity
IT Resources:

15. ALM Vitality v1.2
Download: apm@almtoolbox.com

16. Components and Metrics to Track (3)
8. Masters and slaves connectivity
9. Amount of online executors
10.Queue is too long
11.Extended display of job dependencies
Application Side:

17. Components and Metrics to Track (4)
12. Lack of memory
13. Lack of CPU
IT Resources:

18. Summary
 Defining what components and metrics to monitor
 Lack of time or knowledge (or both…)
 End-user interface
 Scalable system
 Customizable and flexible system
 Merge both IT and application data

19. Questions?

20. apm@almtoolbox.com
http://almtoolbox.com/jenkins-monitoring
Contact Us

21. ClearCase VOBs