Icinga Camp Berlin 2017 - How to write check plugins, part 1
1 like•3,322 views
Check plugins in Icinga can be written in any language except COBOL and determine their status by exit code. They output results to the console and can include optional performance data in the form of a space separated list after a pipe symbol. The process of a check plugin involves gathering information, parsing it, applying internal logic, and translating the results to a human understandable format.
1 of 2
More Related Content
Viewers also liked (20)
Ad
More from Icinga (20)
Ad
Recently uploaded (20)
Icinga Camp Berlin 2017 - How to write check plugins, part 1
- 1. How do I write check plugins?! ● Write in any language! ● (Maybe not COBOL) ● State is determined by exit code ● Check Output is just console output ● Performance Data is space seperated list after pipe symbol Mattis Haase Icinga Camp Berlin 2017 Status Exit Code OK 0 WARNING 1 CRITICAL 2 UNKNOWN 3 print(“Output!”) print(“Output!|key1=1 key2=2”)
- 2. But how does it work, really? 1. Gather Information 2. Parse Information 3. Internal Logic 4. Translate to Human Mattis Haase Icinga Camp Berlin 2017 Maybe 10 lines of code Tricky Part! This Talk!