Talk by Feu Mourek:
Humans are creatures of habit – we have our environments, our tasks, our routine. Building up a routine takes a lot out of us – so as soon as we find something that works for us we stick with it. But is it effective? Are there tools that can make our life so much easier if we manage to integrate them into our routine? Of course, we’re in IT, there are always new and good tools! Only 2 more hurdles to clear – find the right tools for you and actually make the effort to integrate them into your routine.
The purpose of this talk is to help you with exactly that – I will show you the most important quality-of-life modules and add-ons for Icinga.All of them officially supported by the Icinga team and super easy to integrate into your system!
4. Responsibilities Contact Personal
Icinga Web 2:
UX Design,
(Module) Development
feu.mourek@icinga.com Likes pen and paper, video games
and being a nerd
Feu Mourek
Developer
6. Icinga Director
Icinga Configuration and Orchestration Solution
icinga.com/docs/director/
The Director aims to be the favorite Icinga config
deployment tool.
Director is designed for those who want to automate
their configuration deployment and those who want
to grant their “point & click” users easy access to
the configuration. Both at the very same time!
Icinga Director
7. 01
Basics
03
Automation
02
Import & Sync
Icinga Director
Icinga Configuration and Orchestration Solution
Icinga Director not only eases point-and-click configuration but also offers orchestration for
fully automated environments.
Information about network infrastructure and components are often clustered over several
sources. Import from Active Directory and LDAP, databases and cloud providers to have them
all in one place.
Automate everything from import and sync to deployment.
8. 01
Basics
03
Automation
02
Import & Sync
Icinga Director
In a Nutshell
• Make config easy for the end user
• Offer interfaces and integrate other tools
• Avoid writing config files
• Import and sync config from everywhere
• Automate configuration deployment
9. 01
Basics
03
Automation
02
Import & Sync
Icinga Director
Templates
• Everything starts with a template
• Defines what to monitor
• Check command plus settings
• Defines fields and variables
• Zone or agent usage for distributed envs
• Assign apply rules
12. 01
Basics
03
Automation
02
Import & Sync
Icinga Director
Deployment
• Director keeps track of every single change
• Perfect for auditing changes
• Allows to travel back in time
• Pushes configuration to the Icinga 2 API
• Verifies deployment status
16. 01
Basics
03
Automation
02
Import & Sync
Icinga Director
Import & Sync
• Retrieve data from external resources
• Rewrite data with modifiers, e.g. resolve IP addresses
• Define how to map objects
• Detect changes
• Create, update or delete objects
21. 01
Basics
03
Automation
02
Import & Sync
Icinga Director
Automation
• Import, sync and config deployment
• Granular control
• Automatic deployment only at office hours and not more
than one deployment every 10 minutes?
Sure, why not
22. Certificate Monitoring
Discover Your Certificate Infrastructure
icinga.com/docs/x509/
The X.509 module for Icinga Web 2 keeps track of
certificates as they're deployed in a network
environment.
The module's web frontend can be used to view
scan results.
Certificate Monitoring
23. 01
Scan TLS Services
03
Integration
02
Own Trust Store
Certificate Monitoring
Discover Your Certificate Infrastructure
The X.509 modules periodically scans networks (IP and port ranges) for TLS services and
collects whatever certificates it finds along the way.
The certificates are verified using its own trust store.
The module’s web frontend can be used to view scan results, allowing you to drill down into
detailed information about any discovered certificate of your landscape. Further it integrates
with the Director to automatically provide checks for hosts and its discovered TLS services.
24. 01
Scan TLS Services
03
Integration
02
Own Trust Store
• Define scan jobs in the frontend
• Automatically scans every configured IP and port
combination
• Collects new and changed certificates including the
complete certificate chain
• Verifies certificates
• Run jobs on a schedule
Certificate Monitoring
Automatically Scan TLS Services
26. 01
Scan TLS Services
03
Integration
02
Own Trust Store
• Frontend to view scan results
• Detailed information about any certificate and its chain
• Provides hosts and services of collected TLS services
Certificate Monitoring
Integration
28. Business Process
Business Process Modelling
icinga.com/docs/businessprocess/
Create a combined view of your existing data and
build your very own top level view. What matters is
the availability of your whole application or service.
The Business Process Module makes it possible to
set single hosts and services into context.
Business Process
29. 01
Context
03
Visualization
02
Integration
Business Process
Business Process Modelling
Icinga Business Process Modelling allows you to put single hosts and services into context in
order to aggregate their state into the status of your whole application.
Notify and report business processes just like any other host or service.
Tree and tile views, breadcrumb navigation, business impact analysis
34. Icinga Reporting
Insights for Operators and Charts for Stakeholders
icinga.com/docs/reporting/
Icinga Reporting allows you to create and distribute
reports in various output formats.
Icinga Reporting
35. 01
Engine
03
Automation
02
SLA & Availability
Icinga Reporting
Icinga Reporting ships with its own powerful reporting engine for fast and reliable ad-hoc and
scheduled generation and distribution of reports. It supports various output formats, i.e.
HTML, PDF, CSV, JSON.
The SLA and availability reports give you comprehensive views of the overall availability of
your monitored objects during a selected time period and help you to confirm that SLA targets
are being met.
Run reports on a schedule to automatically generate and distribute reports via mail.
Insights for Operators and Charts for Stakeholders
36. 01
Engine
03
Automation
02
SLA & Availability
• Ships with its own engine
• Extensible
• Supports various output formats, i.e. HTML, PDF, JSON,
CSV
• Send reports via mail
• Ad-hoc and scheduled generation
Icinga Reporting
Engine
37. 01
Engine
03
Automation
02
SLA & Availability
• Host and Service SLA
• Filter for groups, custom variables
• Select time frame
• Define target SLA, e.g. 99.5%
• Breakdown
Icinga Reporting
SLA & Availability
39. Icinga Cube
Groups host & service statistics in multiple dimensions
Icinga Cube displays host and service statistics
grouped by various custom variables in a matrix
format.
Icinga Cube
40. 01
Basics
03
Visualization
02
Answers
Icinga Cube
The Cube provides answers to complex queries. Filter by any and everything your variables
and dice it any way you want.
Visualize your data in any way you want and make a dashboard that fits your needs
Groups host & service statistics in multiple dimensions
Icinga Cube works with custom variables that are used to group your hosts and services for a
highly customizable overview.
41. 01
Basics
03
Visualization
02
Answers
• Group by Custom Variables
• Ensure consistency in your environment
• Make connectins by rotating the Cube
• Slice and dice your data
• Integration with Icinga Director
Icinga Cube
Basics
- Here no need to explain icinga
- Overview over a few interesting modules:
Config deployment tool
Use the web ui instead of config files!
SLA = service level agreement
Which project uses how many servers per environment at which location/site?
Who occupies most servers?
How many of those are used in production?
Which project has only development and test boxes?
Which operating system is used for which project and in which environment?
Do we still have Debian Lenny?
Which projects are to blame for this?
Do we have applications where the operating systems used differ in staging and production?
Which project uses which operating system version for which application?
Which projects have homogeneous environments?
Which projects are at a consistent patch level?
How many RHEL 6 variants (6.1, 6.2, 6.3...) do we use?
Who is running the oldest ones? In production?
Which projects are still using physical servers in which environment?