Différences

Ci-dessous, les différences entre deux révisions de la page.

--- report:zabbix:userguide [2026/02/03 13:01] – [PRO version] admin
+++ report:zabbix:userguide [2026/02/04 16:22] (Version actuelle) – admin
@@ Ligne 1: / Ligne 1: @@
-<html><!-- nameoodle --></html>{{ :blocks:logo-apl.png? nolink |}}<html><!-- /nameoodle --></html>
+<html><!-- nomoodle --></html>{{ :blocks:logo-apl.png? nolink |}}<html><!-- /nomoodle --></html>
@@ Ligne 7: / Ligne 7: @@
 ====Overall Presentation====
-The Zabbix report is report plugin performing measurements and data emission to a Zabbix Server and has no direct interface in Moodle. Only global configuration is necessary to ensure operation. The measurement results are exploited in the Zabbix interface, through graphs, recollection screens, or customized dashboards.
+The Zabbix report is report plugin performing measurements and data emission to a Zabbix Server and has **no direct interface** in Moodle. Only global configuration is necessary to ensure operation. The measurement results are exploited in the Zabbix interface, through graphs, recollection screens, or customized dashboards.
 Path : ''Site admin => plugins => reports => zabbix sender''
-====Plugin overview====
-{{ :report:zabbix:plugin-sender.png? nolink&800 |}}
 ====Report configuration====
+{{ :report:zabbix:zabbixreportsettings_1.jpg?1000 |}}
 **Zabbix server protocol ''zabbixprotocol'':** The server's protocol used for administration operations using the zabbix API. the Zabbix server should be directly accessible without redirects. Default : HTTPS
@@ Ligne 23: / Ligne 22: @@
 **Moodle host name in zabbix ''zabbixhostname'':** The host name used to defined the host entry in the Zabbix server configuration. Herein name must match exactly what was used in host definition.
-**Order zabbix_sender ''zabbixsendercmd'':** The location of the "sender" command to send data to Zabbix.  Defaults to: /usr/bin/zabbix_sender
+**zabbix_sender shell command''zabbixsendercmd'':** The location of the "sender" command to send data to Zabbix.  Defaults to: /usr/bin/zabbix_sender
-**User roles ''userrolepolicy'':** Method for determination of user roles. Some methods require special configurations.
+{{ :report:zabbix:zabbixreportsettings_2.jpg?1000 |}}
-**Default:** Resolution based on standard role assignments of moodle.
+**User roles ''userrolepolicy'':** Method for determination of user roles. This determination can be usefull for some values that are indexed to a user role, such as Studetns or Teachers, f.e. when counting connections. Some methods require special configurations. Default: Resolution based on standard role assignments of moodle.
-**Other choice:** Resolution based on profile fields (case of Moodle in ENTs)
+   * Other choice: Resolution based on profile fields (case of Moodle in ENTs)
 **Username Zabbix ''zabbixadminusername'':** The administrator's username who can operate the Zabbix API. This user must have been created in the Zabbix administration. This user does NOT need to access the Zabbix frontend. However, he do needs to read and write in the MOODLE models of the zabbix host associated with Moodle.  Default: admin
@@ Ligne 39: / Ligne 39: @@
 **Definition of the local interface ''interfacedef'':** A method to inform Zabbix server on which network interface it will communicate with this server. Default : By DNS
+{{ :report:zabbix:zabbixreportsettings_3.jpg?1000 |}}
 **In operation ''tellithasstarted'':** By activating this box, you inform Zabbix that this platform is a production environment. This is usefull when grouping moodles in a Moodle Group in Zabbix, so that effective production plaforms can be identified (vs. candidate instances, or preproduction instances).
@@ Ligne 45: / Ligne 47: @@
 **SQL heuristic for exploitation ''tellithasstartedsql'':** An SQL query delivering a result named "started" determines the production state of the operation. Default: Empty
+**Zabbix allowed cron period:** This was recently added for some installations of Moodle using large Moodle arrays (f.e. using [[:local:vmoodle|Moodle Virtualization plugin]]). In that case, we would need to slower down a bit the Zabbix frequency specially for the **instant task** to lower the data recolection technical impact on the installation (we used it f.e. on large array with 350 moodles aside)
+{{ :report:zabbix:zabbixreportsettings_4.jpg?1000 |}}
 **Registration in zabbix:** By using this form, and pursuant your Zabbix administrator remote user is created and has sufficient permissions, you can ask the Zabbix server to register the local host definition that matches this Moodle.
+Once the settings are properly setup, save them once. then, go to the registration process clocking on the link. You will be routed to a confirmation screen:
+{{ :report:zabbix:zabbixregistering.jpg?1000 |}}
+Clicking on the confirmation button will send all the required information to Zabbix to initiate a new host configuration for your Moodle. Of course the administrator user needs to be correctly setup in Zabbix for the registration to work.
 ====PRO version ====
@@ Ligne 52: / Ligne 64: @@
 By entering activation keys obtained from your TMA provider, you will activate the plugin's additional features:
-  * Moodle Plugins local indicators
+  * Moodle Plugins local indicators (See our [[report:zabbix:developerguide|plugin developer guide]] for more details on how designing your specific indicators in your plugins).
-  * Zabbix discovery of Moodle dynamic environment
+  * Zabbix discovery of Moodle dynamic environment (read the additional [[:report:zabbix:discoveringdata|guide for setting up discovery]])
-  * Moodle administrator defined custom measurements (without coding)
+  * [[:report:zabbix:customindicators|Moodle administrator defined custom measurements]] (without coding)
 ----
-<html><!-- nameoodle --></html>
+<html><!-- nomoodle --></html>
 [[:report:zabbix|Back to Zabbix Report index]] - [[:plugins|Back to plugin index]] - [[:start|Back to catalog]]
 <html><!-- /nomoodle --></html>