Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Announcement: development cycle comments #8

Open
kloczek opened this issue Jun 12, 2018 · 2 comments
Open

Announcement: development cycle comments #8

kloczek opened this issue Jun 12, 2018 · 2 comments

Comments

@kloczek
Copy link
Owner

kloczek commented Jun 12, 2018

Hi to everyone who is watching this repo :)

I'm going to create devel branch within next 2-3 days and then start committing few changes which I already have queued like:

  • new php-fpm template
  • few MIB templates updates
  • one new metric and graph in zabbix agent template
  • rewrite Apache template to use master item like it is now in Nginx template.

Up to this moment I will be glad if it will be possible only to review templates, triggers and items descriptions and all README.md files content first.
I'm 100% that it is still a lot to clean on this area :p

Shortly after start work in devel branch hopefully I'll be able to commit tested enough well import_templates script changes. Initially this script will be able to import quickly all templates maintained in this repo. Zabbix has some issues which are kind of obstacles on sharing templates between multiple zabbix servers when when additionally set of those templates are changing.

Without describing now all related details of those issues I think that I can provide procedure of applying such updates in templates allowing to share work results done by many people using additional scripts and few API calls on template update procedure. Here I'm going to use my zapish.inc which is already used in export_templates script.
Nevertheless this will be nothing more than only workaround for some real zabbix issues which sooner or later needs to be solved in zabbix code first. If pressure on solve those issues will be enough hihg because some bunch of people will be sharing some base set of templates I'm sure that Alexey and his team will try to invest some time to address and solve those (already well known) zabbix issues :)
As long as necessary changes will be not implemented straight into zabbix I think that my way of dealing with those issues can provide working solutions of those issues.

If someone already tried to use MIB based templates to assemble monitoring some device please let me know about device type and please submit device template to SNMP Devices/ directory. On submitting such short template with only list of linked other MIB templates please submit result of the commands which I've described on https://github.com/kloczek/zabbix-templates/tree/master/SNMP%20Devices

On sharing those MIB based building blocks templates across many devices monitoring quite important is to verify that results of some changes done in one MIB template on top of one device will have the same or at least similar results in case of using modified/updated MIB template with other device. Different hardware vendors sometimes are embedding in own SNMP agents some changes in code handling even RFCed MIBs.

Happy hacking

kloczek

@kloczek
Copy link
Owner Author

kloczek commented Jun 13, 2018

@kloczek
Copy link
Owner Author

kloczek commented Jun 21, 2018

Short update.
"devel" branch has been added ttps://github.com/kloczek/zabbix-templates/tree/devel
So far in the branch committed changes:

  • New templates
  • Service Zabbix Agent
    • Graphs:
      • new HOST::items which presents number of host items vs number of unsuppoerted item
    • Items:
      • new items with current counter of total host items (supported/unsupprted/enabled/disabled)

@kloczek kloczek changed the title Announcement: 1.0.5 development cycle comments Announcement: development cycle comments Jun 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant