Hi everyone,
I´m pretty new to zabbix, but I love it! :-)
When we startet with zabbix (reading the manual) I just thought: oh my god. This is gonna be hard work. So we rented a consultant. In 10 days, we set up our zabbix (master server in our house; meanwhile about 15 proxies at our customers houses, all proxies automatically start an ssh-tunnel to our server, whole communication over that secure tunnel. Rollout of a new proxy by mindi/mondo and a written script; a new proxy is ready to go from the scatch in about 30min).
But back to the point:
As I was "in" the concept an "thinking" of zabbix (thanks to the great work of our consultant), I had no problem about finding solutions, matching articles in the forum or understanding the manual. I could even help debugging and testing very effective.
So I have to ask: why can I do within 10 days of work that much? Because of our consultant, of course. And why is it not possible to do this on my own, only with the docu?
Because:
- the basic installation is to hard
- when the installation is ready, I didn´t know how to start
- when I startet I did not see "the whole thing", so I was not able to use zabbix strategically; I just was able to guess and click; try and error
- when I saw "the whole thing" I needed so much time for finding a technical way of doing things; begins with finding the right SNMP-OIDs, writing scripts, configuring, configuring, testing, testing; the point: I was missing the best practices / templates
Now, some months later, I got what I want. Nearly all my wishes found there way to zabbix; working fine.
So, what now about the manual. My thinking is, to get the problems away I discribed above (and I think many beginners have the same problems in the same order!):
- we need a good docu about the installation from the scratch, matching the actual release
- it would be great to rollout a vmware-image with the actual zabbix-release; great for beginners; a "certified" installation. I think this would be also be great for testing. Offen, a problem is laying in a miss-configuration. With a "certified installation", we all have ONE SIMILAR base we can discuss on; maybe - in the style of open source - upgrade and perfect it all together (backup processes, scripts, etc.)
- we need a visual thing, discribing "the whole thing". Maybe a Visio-sheet or something, just visualizing, what zabbix can do all over
- we need a good documentation and matching best practices (Templates, read-and-click-descriptions)
Let´s come to the "how to write the docu". In my work I often have to write documentations; for beginners and users, for pros or myself. The one thing I found in all situations: a large document, just giving one point after the other one (PDF, DOC, etc.) is not a practicable thing. It gives you a good feeling ("I have done my work"), but it is far away from "I can work with it an I really NEED it".
So, I think, the best way of implementing a docu is a wiki. BUT: I would "implement" it in zabbix!!!! The zabbix-developers have implemented a "?" in zabbix, pointing to the downloadpage of the PDF-docu.
Exactly this "?" I would use on every page and needed situation to point to the right page in the wiki. So we setup up a wiki exactly in the way, zabbix is structured:
- Main page Monitoring
- Dashboard
- ...
- Configuration
- Hosts
- ...
When I´m by configuring a new item, I just click the ? and come to the wiki to the item-section.
Every section is structured exactly the same:
for example:
1.) Screenshot of the page
2.) short discription of every button, setting, etc.
3.) Best practices to the section (for example creating an item to monitor a DELL-RAID-Controller)
4.) Downloadsection for needy tools, templates, screenshots from users, etc.
What remains is the question, if it is still needed to HAVE a PDF. I don´t think so; maybe because I´m working that much paper-less. If needed, I can (with a printerfriendly wiki) print me out the section, that I need.
Merry christmas to everybody!
Markus.
I´m pretty new to zabbix, but I love it! :-)
When we startet with zabbix (reading the manual) I just thought: oh my god. This is gonna be hard work. So we rented a consultant. In 10 days, we set up our zabbix (master server in our house; meanwhile about 15 proxies at our customers houses, all proxies automatically start an ssh-tunnel to our server, whole communication over that secure tunnel. Rollout of a new proxy by mindi/mondo and a written script; a new proxy is ready to go from the scatch in about 30min).
But back to the point:
As I was "in" the concept an "thinking" of zabbix (thanks to the great work of our consultant), I had no problem about finding solutions, matching articles in the forum or understanding the manual. I could even help debugging and testing very effective.
So I have to ask: why can I do within 10 days of work that much? Because of our consultant, of course. And why is it not possible to do this on my own, only with the docu?
Because:
- the basic installation is to hard
- when the installation is ready, I didn´t know how to start
- when I startet I did not see "the whole thing", so I was not able to use zabbix strategically; I just was able to guess and click; try and error
- when I saw "the whole thing" I needed so much time for finding a technical way of doing things; begins with finding the right SNMP-OIDs, writing scripts, configuring, configuring, testing, testing; the point: I was missing the best practices / templates
Now, some months later, I got what I want. Nearly all my wishes found there way to zabbix; working fine.
So, what now about the manual. My thinking is, to get the problems away I discribed above (and I think many beginners have the same problems in the same order!):
- we need a good docu about the installation from the scratch, matching the actual release
- it would be great to rollout a vmware-image with the actual zabbix-release; great for beginners; a "certified" installation. I think this would be also be great for testing. Offen, a problem is laying in a miss-configuration. With a "certified installation", we all have ONE SIMILAR base we can discuss on; maybe - in the style of open source - upgrade and perfect it all together (backup processes, scripts, etc.)
- we need a visual thing, discribing "the whole thing". Maybe a Visio-sheet or something, just visualizing, what zabbix can do all over
- we need a good documentation and matching best practices (Templates, read-and-click-descriptions)
Let´s come to the "how to write the docu". In my work I often have to write documentations; for beginners and users, for pros or myself. The one thing I found in all situations: a large document, just giving one point after the other one (PDF, DOC, etc.) is not a practicable thing. It gives you a good feeling ("I have done my work"), but it is far away from "I can work with it an I really NEED it".
So, I think, the best way of implementing a docu is a wiki. BUT: I would "implement" it in zabbix!!!! The zabbix-developers have implemented a "?" in zabbix, pointing to the downloadpage of the PDF-docu.
Exactly this "?" I would use on every page and needed situation to point to the right page in the wiki. So we setup up a wiki exactly in the way, zabbix is structured:
- Main page Monitoring
- Dashboard
- ...
- Configuration
- Hosts
- ...
When I´m by configuring a new item, I just click the ? and come to the wiki to the item-section.
Every section is structured exactly the same:
for example:
1.) Screenshot of the page
2.) short discription of every button, setting, etc.
3.) Best practices to the section (for example creating an item to monitor a DELL-RAID-Controller)
4.) Downloadsection for needy tools, templates, screenshots from users, etc.
What remains is the question, if it is still needed to HAVE a PDF. I don´t think so; maybe because I´m working that much paper-less. If needed, I can (with a printerfriendly wiki) print me out the section, that I need.
Merry christmas to everybody!
Markus.

Comment