Diese Präsentation wurde erfolgreich gemeldet.
Die SlideShare-Präsentation wird heruntergeladen. ×

Alexei Vladishev - Opening Speech | ZabConf2016

Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Anzeige
Nächste SlideShare
Agility in 2016
Agility in 2016
Wird geladen in …3
×

Hier ansehen

1 von 69 Anzeige

Alexei Vladishev - Opening Speech | ZabConf2016

Herunterladen, um offline zu lesen

Alexei will talk about new exciting features of Zabbix 3.2 event correlation module aimed to simplify large scale monitoring and root cause analysis. Also sharing his thoughts about future plans in regards of Zabbix 3.4 and further releases.

Alexei will talk about new exciting features of Zabbix 3.2 event correlation module aimed to simplify large scale monitoring and root cause analysis. Also sharing his thoughts about future plans in regards of Zabbix 3.4 and further releases.

Anzeige
Anzeige

Weitere Verwandte Inhalte

Andere mochten auch (20)

Ähnlich wie Alexei Vladishev - Opening Speech | ZabConf2016 (20)

Anzeige

Aktuellste (20)

Anzeige

Alexei Vladishev - Opening Speech | ZabConf2016

  1. 1. Welcome to Zabbix Conference 2016! 1
  2. 2. Who am I? Alexei Vladishev Creator of Zabbix CEO, Architect and Product Manager Twitter: @avladishev 2
  3. 3. Our sponsors 3
  4. 4. Conference stats 4
  5. 5. 223 participants from 38 (+10) countries 5
  6. 6. 223 participants from 38 countries 6
  7. 7. Top five countries 1. ……. 16 2. France 13 3. Netherlands 11 4. Lithuania 10 5. Germany 9
 
 * excluding Latvia 7
  8. 8. Top five countries 1. Russia 16 2. France 13 3. Netherlands 11 4. Lithuania 10 5. Germany 9
 
 * excluding Latvia 8
  9. 9. What’s happened in 2016 9
  10. 10. Release of Zabbix 3.0 LTS 10 Long Term Support (LTS) till 2021
  11. 11. Faster development, better support 11 45 people in Riga, Tokyo and New York
  12. 12. Last but not least… 12 Zabbix is a True Open Source software and will always be.
  13. 13. Let’s talk about Zabbix 3.2 13
  14. 14. Quick reminder Zabbix 3.2 is the next major release, non LTS, 6-7 months support period 14
  15. 15. Event correlation 15
  16. 16. Example of a local event correlation 16
  17. 17. Log file monitoring 17 … 10/Aug/2016:06:25:30 service Jira stopped 10/Aug/2016:06:25:32 service MySQL stopped 10/Aug/2016:06:26:11 service MySQL started 10/Aug/2016:06:26:22 service Redis stopped 10/Aug/2016:06:26:58 service Redis started 10/Aug/2016:06:27:31 service Jira started … /var/log/services.log How many items and triggers we need to monitor state of each service and have independent notification?
  18. 18. Zabbix 3.2: One item and one trigger to monitor all services! 18
  19. 19. 19
  20. 20. 20
  21. 21. How will it work? 21 10/Aug/2016:06:25:30 service Jira stopped “Service Jira stopped” PROBLEM
  22. 22. 10/Aug/2016:06:25:30 service Jira stopped “Service Jira stopped” PROBLEM 10/Aug/2016:06:27:32 service MySQL stopped “Service MySQL stopped” PROBLEM How will it work? 22
  23. 23. 10/Aug/2016:06:25:30 service Jira stopped “Service Jira stopped” PROBLEM 10/Aug/2016:06:27:32 service MySQL stopped “Service MySQL stopped” RESOLVED 10/Aug/2016:06:28:11 service MySQL started How will it work? 23
  24. 24. 10/Aug/2016:06:25:30 service Jira stopped “Service Jira stopped” PROBLEM 10/Aug/2016:06:27:32 service MySQL stopped “Service MySQL stopped” RESOLVED 10/Aug/2016:06:28:11 service MySQL started 10/Aug/2016:06:34:22 service Redis stopped “Service Redis stopped” PROBLEM How will it work? 24
  25. 25. 10/Aug/2016:06:25:30 service Jira stopped “Service Jira stopped” PROBLEM 10/Aug/2016:06:27:32 service MySQL stopped “Service MySQL stopped” RESOLVED 10/Aug/2016:06:28:11 service MySQL started 10/Aug/2016:06:34:22 service Redis stopped “Service Redis stopped” RESOLVED 10/Aug/2016:06:37:58 service Redis started How will it work? 25
  26. 26. 10/Aug/2016:06:25:30 service Jira stopped “Service Jira stopped” RESOLVED 10/Aug/2016:06:27:32 service MySQL stopped “Service MySQL stopped” RESOLVED 10/Aug/2016:06:28:11 service MySQL started 10/Aug/2016:06:34:22 service Redis stopped “Service Redis stopped” RESOLVED 10/Aug/2016:06:37:58 service Redis started 10/Aug/2016:06:55:31 service Jira started How will it work? 26
  27. 27. Tags give us ability to switch from host- to service-centric problem reporting and notifications 27
  28. 28. But it’s not limited only to services! 28
  29. 29. Service: Oracle Service: {{ITEM.VALUE}.regsub(‘…’, ’1 2’)} Datacenter: NY2 Datacenter: {$DATACENTER} Area: Performance Area: Availability Area: Security Environment: Staging Environment: Test User impact: None User impact: Critical 29 Different dimensions
  30. 30. 30 So many problems
  31. 31. 31 By environment: Production
  32. 32. 32 By datacenter: NY2
  33. 33. 33 By impact: Critical
  34. 34. 34 By impact: Critical AND in NY2
  35. 35. Problem view 35
  36. 36. 36
  37. 37. Filtering! 37
  38. 38. 38
  39. 39. Notifications 39
  40. 40. 40
  41. 41. Global correlation 41
  42. 42. 42 Correlation rules Existing problems New problem comes ?
  43. 43. 43 Correlation rules Existing problems No correlation found
  44. 44. 44 Correlation rules Existing problems Close older problems
  45. 45. 45 Correlation rules Existing problems New problem will be closed immediately
  46. 46. 46
  47. 47. 47
  48. 48. Problem tags and correlation is a solid foundation for further improvements 48
  49. 49. Nested host groups 49 Servers Servers/Physical Servers/VMs Location/Africa Location/Europe Location/Japan Location/North America Templates Templates/Official Templates/SNMP Templates/Services Templates/Vendors Templates/Vendors/HP
  50. 50. 50 Redesigned permissions
  51. 51. 51 Filtering
  52. 52. Manually close problems 52
  53. 53. 53
  54. 54. 54
  55. 55. Trigger hysteresis? Easy! 55
  56. 56. 56
  57. 57. Viewable items, triggers, graphs created by LLD 57
  58. 58. 58 Items Triggers
  59. 59. Better actions and escalations 59
  60. 60. 60
  61. 61. 61
  62. 62. Web scenario export/import Function evaluation for NOTSUPPORTED items Coping with fast-growing log files Support of regex in count () and much more! 62 Also…
  63. 63. For detailed list of new features see Documentation of Zabbix 3.2 63
  64. 64. Zabbix 3.2 is a result of active cooperation with our partners and customers. 64 Special thanks to S&T Slovakia s.r.o.
  65. 65. How to upgrade? 65
  66. 66. Nothing special, except … Some history tables are affected: history_log, history_text It may take time to execute depending on size of log and text data stored in the database 66
  67. 67. Where is Zabbix 3.2? 67
  68. 68. Zabbix 3.2.0 is expected to be released very soon 68
  69. 69. Enjoy the conference! 69 Thanks for your support

×