Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- server:zabbix [2022/12/05 11:36] – [Problembehebung] st
+++ server:zabbix [2023/03/06 20:04] (aktuell) – [Signal] st
@@ Zeile 232: / Zeile 232: @@
 Am Ende der Installation ist der Login mit "Admin" und Passwort "zabbix" möglich.
-===== Server und Datenbank tuning =====
+===== Datenbank =====
+**Größe der Datenbank** "zabbix": <code sql> SELECT table_schema "zabbix", sum(data_length + index_length)/1024/1024 "DВ size in MB" FROM information_schema.TABLES GROUP BY table_schema;</code>
+**Größe der zabbix Tabellen**: <code sql>use
+SELECT
+  TABLE_NAME AS `Table`,
+  ROUND((DATA_LENGTH + INDEX_LENGTH) / 1024 / 1024) AS `Size (MB)`
+FROM
+  information_schema.TABLES
+WHERE
+  TABLE_SCHEMA = "zabbix"
+ORDER BY
+  (DATA_LENGTH + INDEX_LENGTH)
+DESC;
+</code>
+==== housekeeping ====
+Seit Zabbix 6.0 kann das audit log größer werden (u.a. werden discovery-aktionen von Benutzer SYSTEM geloggt):
+  * Administration -> General -> Audit log ( https://$ZABBIX_SERVER/zabbix/zabbix.phpaction=audit.settings.edit ):
+==== housekeeping ====
+Administration -> General -> Housekeeping ( https://$ZABBIX_SERVER/zabbix/zabbix.php?action=housekeeping.edit )
+    * Override item history period: 30, ... 90d ?
+    * ...?
+[[https://www.zabbix.com/documentation/3.0/manual/concepts/server|zabbix housekeeper laufen lassen]] (manuell): <code bash>zabbix_server -c /etc/zabbix/zabbix_server.conf -R housekeeper_execute</code>
+manuelles clean-up der Datenbank (vorher BACKUP!):
+<code sql>
+-- intervals in days
+SET @history_interval = 30;
+SET @trends_interval = 90;
+DELETE FROM alerts WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);
+DELETE FROM acknowledges WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);
+DELETE FROM events WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);
+DELETE FROM history WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);
+DELETE FROM history_uint WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);
+DELETE FROM history_str WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);
+DELETE FROM history_text WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);
+DELETE FROM history_log WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@history_interval * 24 * 60 * 60);
+DELETE FROM trends WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@trends_interval * 24 * 60 * 60);
+DELETE FROM trends_uint WHERE (UNIX_TIMESTAMP(NOW()) - clock) > (@trends_interval * 24 * 60 * 60);
+</code>
+===== Poller ausgelastet =====
-Größe der Datenbank: <code sql> SELECT table_schema "zabbix", sum(data_length + index_length)/1024/1024 "DВ size in MB" FROM information_schema.TABLES GROUP BY table_schema;</code>
 Zabbix meldet wenn bestimmt Poller ausgelastet sind (viele Proxies, viele System nicht erreichbar etc.)
@@ Zeile 302: / Zeile 350: @@
 <code bash>
-apt-get install libunixsocket-java default-jre --no-install-recommends
+# noch nötig?
-wget https://github.com/AsamK/signal-cli/releases/download/v0.7.4/signal-cli-0.7.4.tar.gz
+# apt install libunixsocket-java default-jre --no-install-recommends
-wget https://github.com/AsamK/signal-cli/releases/download/v0.7.4/signal-cli-0.7.4.tar.gz
+# auf aktuelle Version ändern:
-tar xfv signal-cli-0.7.4.tar.gz -C /opt
+export VERSION=0.11.7
+wget https://github.com/AsamK/signal-cli/releases/download/v"${VERSION}"/signal-cli-"${VERSION}"-Linux.tar.gz
-ln -sf /opt/signal-cli-0.7.4/bin/signal-cli /usr/local/bin/
+sudo tar xf signal-cli-"${VERSION}"-Linux.tar.gz -C /opt
+sudo ln -sf /opt/signal-cli-"${VERSION}"/bin/signal-cli /usr/local/bin/
 # (besser in /etc/sudoers.d):
@@ Zeile 314: / Zeile 363: @@
 <file>
-zabbix  ALL=(root) NOPASSWD: /opt/signal-cli-0.7.4/bin/signal-cli
+zabbix  ALL=(root) NOPASSWD: /opt/signal-cli-0.11.7/bin/signal-cli
 </file>