trouble ticket integration with zabbix in large environment
TRANSCRIPT
Trouble Ticket Integration with Zabbix in Large Environment
2016 Sept
Presentation
Page 3
Summary
1. Introduction2. Issues3. Plugin Architecture4. External Specifications5. Technical Details
Page 4
Page 5
-> What are we talking about ?
-> Large Environment ?
-> Trouble Ticket ?
Part 1Introduction
What are we talking about ?
Zabbix TroubleTicket Connexion→ Two ways connexion→ APIs→ Connector Database (Zabbix TroubleTicket Link)
Large Environment→ 1000 tickets per day
Page 6
Trouble Ticket ?
• Lists of issues (Most of the time : Source = mail or phone)
• Manage issues (Most of the time through HelpDesk)
→ ServiceNow is a SaaS Trouble Ticketing System widely used in Large environments
Page 7
What is a Large Environment ?
• More than 14 000 servers , 1 million items
• Some servers with over 10 000 items• Some servers with over 10 000 triggers• More than 100 Zabbix administrators
developping Application Templates
Page 8
Part 2Issues
Page 9
The Problem
Large Environments rely on TroubleTicket tool and HelpDesk for managing IT issues. Bridging Zabbix with over 5000 servers and HelpDesk manually is a painful and impossible project.
Page 10
SwissLife Case Study
Page 11
SwissLife Presentation
Page 12
SwissLife Presentation
Page 13
Part 3Plugin Architecture
Page 14
Page 15
Plugin Architecture
Page 16
Plugin Architecture
Page 17
Plugin Architecture
Part 4External Specifications
Page 18
Page 19
Some of the Functionalities
→ Opens automatically a ServiceNow Ticket via Snow APIsFull Automatic (based on Trigger name TR--A)Manual (TR--M), needs acknowledge from operator
→ Fill in automatically Snow fields with Zabbix macrosCaller, Environment, CI, Application, Server, Team, Category,
Subcategory, Dates,…→ Correlate Zabbix events automatically with Snow tickets
(same trigger source)→ Correlate Zabbix events manually with Snow tickets
(different triggers sources)→ Sends back Correlation confirmations to Operators→ Monitor Snow tickets status and update Zabbix via APIs
when ticket is closed or resolved→ Others: http proxy, debug, logs, ...
Page 20
Triggers Nomenclature
TR--A/M--PRD/HPR--{$SERVICEXXX}--{$CIXXX}--Free Description of Trigger | Auto/Manu |
Prod or Non Prod | Service (~ Application Name) |
CI (could be Server or Oracle DB, …) | Free Description
Nota Bene: Some détails come from Host Inventory
Page 21
External Specifications
Page 22
External Specifications
Part 5Technical Details
Page 23
Page 24
Automatic Tickets
Page 25
Automatic Tickets
Page 26
Automatic Tickets
Page 27
Automatic Tickets
Page 28
Automatic Tickets
Page 29
Manual Tickets
Page 30
Manual Tickets
Page 31
Manual Tickets : noticket
Page 32
Manual Tickets : link to ticket
Page 33
Zabbix Events Correlation
Connector Database
Page 34
Page 35
Connector Database
Page 36
Code
Page 37
Supported Versions
Connector Release V6 synchronized with :
- Zabbix V2.2.x (must be OK with 2.4 and 3.0 but not tested)
- ServiceNow Fuji Version
Released as OpenSourceOn Zabbix Share
Page 38
Merci pour votre attention !
Alain Ganuchaud
Cool [email protected]
Questions?
Page 39
Follow us on Twitter: @zabbix_fr @AlainGanuchaud