Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Icinga Web 2 is more

Thomas Gelf talking about Icinga Web 2 and additional modules at Icinga Camp 2016 in Portland.

Icinga Web 2 is more

  1. 1. www.icinga.org Icinga Web 2 is more... IcingaCamp - Portland – 10/10/15
  2. 2. Thomas Gelf Web 2 Product owner Prototyping beast Principal Consultant @netways
  3. 3. AGENDA
  4. 4. • Icinga Web 2 is now stable • LOTS of modules in the pipeline • I'll show a few of them
  5. 5. GRAPHING TIME SERIES DATA
  6. 6. • Good old times ;-) • Web 2: generic grapher hook • We want to support all of them • Open Source is about working together
  7. 7. • PNP4Nagios integration • Available on GitHub and git.icinga.org • Very simple, based on iFrames
  8. 8. ROADMAP Deeper integration, direct rendering • (using/supporting legacy templates) • Afterwards it should be tagged stable
  9. 9. MORE IDEAS (1) • Index massive amounts of RRD files in a database for faster lookups • Working prototype with 200,000 datasources running in production • Billions of datapoints on a single server
  10. 10. MORE IDEAS (2) • A customer asked for reports like: • Graph all (1000s) 3G/UMTS links • "Worst ones first" • (means order them by antenna gain, using the daily/weekly/monthly standard deviation) • RRD is still one of the fastest NoSQL databases for time series data
  11. 11. DO MORE WITH GRAPHITE
  12. 12. • Not designed to replace Grafana • Fills the gap where Grafana fails • Multiple (many) instances of one thing • Lots of information at first sight • Many CPUs, hundreds of interfaces
  13. 13. ROADMAP Allow one to configure distinct trees (Icinga2 hosts, services, CollectD...) • Ship nice templates for ITL checks • Will be released very soon l Needs Icinga 2.4
  14. 14. WHAT ELSE? • Implementing a basic hook is easy • We'd like to see support for more tools • Think of Munin, Cacti, Prometheus...
  15. 15. REPORTING
  16. 16. Extensible reporting module • configurable timeranges • access monitored objects • enforce restrictions • hook for concrete implementations
  17. 17. MODEL BUSINESS PROCESSES
  18. 18. • Hundreds of nodes are not an issue • Thousands also, but they hurt your web browser • It's therefore perfectly valid to define sub-nodes referencing processes defined elsewhere
  19. 19. • Alert based on business processes • Generate availability reports (SLA) • How? Define Icinga checks! • Hint: use Puppet to generate processes
  20. 20. ROADMAP • Publicly available since a long time • TBD: improve the process editor • Stable release within next weeks
  21. 21. RENDER MAPS
  22. 22. • Authentication and authorization • Permissions and restrictions based on Icinga Web 2 roles • Add preferred maps to main menu
  23. 23. • Seen in the wild: Google Maps integration
  24. 24. ROADMAP • No concrete schedule • Basically production-ready • Guess we should tag and publish it ;)
  25. 25. INTEGRATE YOUR TTS
  26. 26. • Trouble tickets • Just one more generic hook • We (and others) did already a couple of implementations
  27. 27. Already on GitHub: generictts
  28. 28. Request Tracker – RT. Used internally, needs cleanup, will be published.
  29. 29. Helpline. Customer-specific implementation, deeply integrated.
  30. 30. Elasticsearch / Logstash: quick access
  31. 31. ACCESS YOUR LOGS
  32. 32. Elasticsearch / Logstash: quick access
  33. 33. ROADMAP • Implement an Elastic Search query renderer for our powerful filters • Will allows us to enforce ACLs • We want to have it soon, but no concrete schedule right now
  34. 34. MANAGE SNMP TRAPS
  35. 35. JUST ONE MESSAGE
  36. 36. IMMAGINE THESE TOGETHER
  37. 37. ROADMAP • None. • We developed working prototypes for all required components • Sponsorship could really help here
  38. 38. INTEGRATE Icinga Web 2
  39. 39. • Icinga 2 is multithreaded • Load is distributed automatically • Monitors in a second interval
  40. 40. CONFIGURATION MADE EASY
  41. 41. Target audience • Point & click users • Fully automated environments • At the very same time (!!)
  42. 42. Icinga loves automation • Perfectly fit for Puppet • Collect exported resources or query PDB to build Icinga config • You basically define hosts equipped with custom vars • Services are mostly apply rules based on host properties
  43. 43. Monitoring has to „just work“ • No one wants to waste time on it • But not every system is fully automated • e.g. „Add a new MSSQL instance“ • Environmental sensors
  44. 44. Deploying every few minutes? • Don't want to wait for next Puppet run? • New hosts or apps need to be actively monitored seconds after being deployed
  45. 45. Sync... ...like a pro!
  46. 46. Demo
  47. 47. ROADMAP • Release scheduled for November • Needs Icinga 2.4
  48. 48. WRITE YOUR OWN MODULES
  49. 49. Demo
  50. 50. Thank You! www.icinga.org dev.icinga.org git.icinga.org @icinga /icinga +icinga
  51. 51. QUESTIONS? Thomas Gelf <thomas.gelf@netways.de>
  52. 52. BEER!

×