Skip to content

Commit

Permalink
main menu explained in detail
Browse files Browse the repository at this point in the history
  • Loading branch information
Patrik Uytterhoeven authored and Patrik Uytterhoeven committed Dec 6, 2023
1 parent 648b0fa commit 93f3747
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 11 deletions.
2 changes: 1 addition & 1 deletion docs/01-Getting started with Zabbix.md
Original file line number Diff line number Diff line change
Expand Up @@ -810,7 +810,7 @@ zabbix=> SELECT session_user, current_user;
(1 row)
```

PostgreSQL works a bit different then MySQL or MariqDB when it comes to almost everything :) One of the things that it has that MySQL not has are for example shemas. If you like to know more about it i can recommend [this](https://hevodata.com/learn/postgresql-schema/#schema) URI. It explains in detail what it is and why we need it. But in short ... In PostgreSQL schema enables a multi-user environment that allows multiple users to access the same database without interference. Schemas are important when several users use the application and access the database in their way or when various applications utilize the same database. There is a standard schema that you can use but the better way is to create our own schema.
PostgreSQL works a bit different then MySQL or MariaDB when it comes to almost everything :) One of the things that it has that MySQL not has are for example shemas. If you like to know more about it i can recommend [this](https://hevodata.com/learn/postgresql-schema/#schema) URI. It explains in detail what it is and why we need it. But in short ... In PostgreSQL schema enables a multi-user environment that allows multiple users to access the same database without interference. Schemas are important when several users use the application and access the database in their way or when various applications utilize the same database. There is a standard schema that you can use but the better way is to create our own schema.

???+ Note
There is a standard schema ```public``` that you can use but the better way is to create our own schema this was if later something else is installed next to the Zabbix database it will be easier to create users with only access to the newly created database tables.
Expand Down
18 changes: 9 additions & 9 deletions docs/02-Starting with the basic configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -126,9 +126,9 @@ It's important to know that we have so far seen our dashboard with the Admin use
![Menu by user](CH02/monitoring-menu.png){ align=right width="180" }

* Problems: This page will give us an overview of all the problems. With filter we can look at recent problems past problems and problems that are active now. There are many more filters tor drill down more.
* Hosts: will give us a quick overview page with whats happening on our hosts and allows us to quickly go to the latest data, graphs and dashboards.
* Hosts: This will give us a quick overview page with whats happening on our hosts and allows us to quickly go to the latest data, graphs and dashboards.
* Latest data: This page I probably use the most, it shows us all the information collected from all our hosts.
* Maps: is the location where we can create map that are an oveview of our IT infrastructure very useful to get a high level overview of the network.
* Maps: The location where we can create map that are an oveview of our IT infrastructure very useful to get a high level overview of the network.
* Discovery: When we run a network discovery this is the place where we can find the results.

---
Expand All @@ -150,13 +150,13 @@ It's important to know that we have so far seen our dashboard with the Admin use

![Menu by user](CH02/reports-menu.png){ align=left width="180" }

* System information:
* Scheduled reports:
* Availability report:
* Top 100 triggers:
* Audit log:
* Action log:
* Notifications:
* System information: System information is a summary of key Zabbix server and system data.
* Scheduled reports: The place where we can schedule our reports, a pdf of the dashboard that will be sent at a specified time and date.
* Availability report: A nice overview where we can see what trigger has been in ok/nok state for how much % of the time
* Top 100 triggers: Another page I visit a lot here we have our top list with triggers that have been in a nok state.
* Audit log: An overview of the user activity that happend on our system. Useful if we want to know who did what and when.
* Action log: A detailed overview of our actions can be found here. What mail was sent to who and when ...?
* Notifications: A quick overview of the number of notifications sent to each user.

---

Expand Down
2 changes: 1 addition & 1 deletion docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ Hi, welcome and thank you for your interest in my Zabbix book. I wrote the [Zabb
As Zabbix is an opensource product and making money out of the books was never my intention, it got me thinking how to do things different.
How to make a new book without using a publisher like I had done before.
After a while, I came up with the idea to make a book that would be free and that would be updated when new versions came out.
Since I am a huge fan of documetation in markdown or asciidoc I came up with the idea to share the book in git and use markdown.
Since I am a huge fan of documentation in markdown or asciidoc I came up with the idea to share the book in git and use markdown.
The only problem left was how to make those markdown files readable in an easy way like a book ? After some searching trying to look for a good solution I found [MkDocs](https://www.mkdocs.org). MkDocs is a Python-Markdown library that can convert everything to HTML and can be templated. So the problem was solved and a new book was born.


Expand Down

0 comments on commit 93f3747

Please sign in to comment.