Differences

This shows you the differences between two versions of the page.

--- cluster:183 [2019/08/14 16:02]
hmeij07 [Zenoss]
+++ cluster:183 [2024/10/15 19:17] (current)
hmeij07
@@ Line 1: / Line 1: @@
 \\
 **[[cluster:0|Back]]**
+We have moved away from Zenoss, it was getting too old and throwing false alerts. It relies on SNMP and we wnated to go agent based. For the speed of installion we first installed Ganglia (not developed anymore but an awesome package based tool). Then we added Zabbix for completion.  Details at [[cluster:227|HPC Monitoring]]
+ --- //[[hmeij@wesleyan.edu|Henk]] 2024/10/15 19:14//
 ==== Zenoss ====
-Our scratch server has been our Zenoss server since the beginning. Ran RHEL 5.5 and is now decommissioned. A new server has deployed to only do the Zenoss service.  It will run CentOS 6.10 (Final) and Zenoss 4.2.5, specifically the Community Edition last v4 version because I like to keep it simple. All we want is basic monitoring, alerts when nodes go down, and historical data.
+Our scratch server has been our Zenoss server since the beginning. Ran RHEL 5.5 and is now decommissioned. A new server has been deployed to only do the Zenoss service.  It will run CentOS 6.10 (Final) and Zenoss 4.2.5, specifically the Community Edition last v4 version because I like to keep it simple. All we want is basic monitoring, alerts when nodes go down, and historical data.
 <code>
@@ Line 27: / Line 31: @@
 At this point the script fails to find the core rpm file for my distro. Luckily, there are some folks maintaining the script for 4.2.5 and pointing to the new location. Shout out to Jane, much appreciated!
-[[https://github.com/jcurry/Zenoss_4.2.5_core-autodeploy|Zenoss_4.2.5_core-autodeploy]]
+Download the zip file from github.com [[https://github.com/jcurry/Zenoss_4.2.5_core-autodeploy|Zenoss_4.2.5_core-autodeploy]]
 <code>
-# Download the zip file from github.com
 # Stage the maintained autodeploy script
@@ Line 87: / Line 89: @@
 </code>
-You may want to copy the secure_zenoss.sh script and edit it to only keep the Mysql admin password code block.
+You may want to copy the secure_zenoss.sh script and edit it to only keep the Mysql admin password code block to secure your MySQL installation.
+''yum install postfix'' then configure email delivery, define relay_host in ''main.cf''
+Last but not least define a ''Trigger'' (production, critical) and associate with a ''Notification'' (email, clear) ...\\
+ read [[http://wiki.zenoss.org/Notify_Me_of_Important_Events|Notify_Me_of_Important_Events Link]]  ... do check "send only on initial occurrence"
+http://wiki.zenoss.org/Main_Page
+From wesleyan.edu you can log in as guest/WelcomeGuest
 \\
 **[[cluster:0|Back]]**

DokuWiki

User Tools

Site Tools

Differences

Page Tools