Zenoss - Revision history

Chet at 15:29, 17 July 2012

2012-07-17T15:29:51Z

Drobbins: /* zends */

2012-05-07T17:36:00Z

‎zends

Drobbins: /* Stopping Daemons */

2012-02-13T22:59:22Z

‎Stopping Daemons

Drobbins: /* zeneventserver */

2012-02-13T22:58:35Z

‎zeneventserver

Drobbins: /* zends */

2012-02-13T22:58:21Z

‎zends

Drobbins: /* ZenPacks */

2012-02-13T22:57:25Z

‎ZenPacks

Drobbins at 22:57, 13 February 2012

2012-02-13T22:57:03Z

Drobbins at 22:54, 13 February 2012

2012-02-13T22:54:00Z

Drobbins at 22:53, 13 February 2012

2012-02-13T22:53:05Z

Drobbins: /* zends */

2012-02-13T22:47:10Z

‎zends

@@ Line 131: / Line 131: @@
 This will cause zenoss to skip the commented-out daemons and only start the daemons you need. You can always come back to the <tt>daemons.txt</tt> file and modify it as necessary as you utilize more Zenoss functionality in the future. In the mean-time, your memory footprint will be a bit smaller :)
 [[Category:Featured]]
 [[Category:DevOps]]

@@ Line 23: / Line 23: @@
 This section will document some steps you can use to make Zenoss more memory-efficient.
-=== zends ===
+=== MySQL/zends ===
-Zends is a commercially-licensed version of [[MySQL]] that is included with Zenoss Service Dynamics. By default, it is tuned to handle up to 2000 devices. For smaller installations, the pool and cache sizes may be a bit high.
+Zenoss Core 4 uses MySQL.
-To change settings for <tt>zends</tt>, edit <tt>/opt/zends/etc/zends.conf</tt>. Change <tt>innodb_buffer_pool_size</tt> to a smaller value, such as <tt>256M</tt>. You can also lower the other sizes accordingly. Suggested minimal configuration:
+The commercial version of Zenoss uses zends. Zends is a commercially-licensed version of [[MySQL]] that is included with Zenoss Service Dynamics. By default, it is tuned to handle up to 2000 devices. For smaller installations, the pool and cache sizes may be a bit high.
 <pre>
@@ Line 38: / Line 40: @@
 You will need to edit this file as <tt>root</tt>. After making changes, perform the following steps:
 <console>

@@ Line 122: / Line 122: @@
 </console>
-This will cause zenoss to skip the commented-out daemons and only start the daemons you need. You can always come back to the <tt>daemons.txt</tt> file and modify it as necessary as you utilize more zenoss functionality.
+This will cause zenoss to skip the commented-out daemons and only start the daemons you need. You can always come back to the <tt>daemons.txt</tt> file and modify it as necessary as you utilize more Zenoss functionality in the future. In the mean-time, your memory footprint will be a bit smaller :)
 [[Category:Featured]]
 [[Category:DevOps]]

@@ Line 47: / Line 47: @@
 === zeneventserver ===
-Zeneventserver is a new Java-based event server for Zenoss and is written in Java. By default, it will allow the Java heap to get quite large. This can be modified by editing the <tt>/opt/zenoss/bin/zeneventserver</tt> script and appending an <tt>-Xmx512m</tt> option to the <tt>DEFAULT_ZEP_JVM_ARGS</tt> file, as follows:
+Zeneventserver is a new Java-based event server for Zenoss. By default, it will allow the Java heap to get quite large. This can be modified by editing the <tt>/opt/zenoss/bin/zeneventserver</tt> script and appending an <tt>-Xmx512m</tt> option to the <tt>DEFAULT_ZEP_JVM_ARGS</tt> file, as follows:
 <pre>

@@ Line 27: / Line 27: @@
 Zends is a commercially-licensed version of [[MySQL]] that is included with Zenoss Service Dynamics. By default, it is tuned to handle up to 2000 devices. For smaller installations, the pool and cache sizes may be a bit high.
-To change settings for <tt>zends</tt>, edit <tt>/opt/zends/etc/zends.conf</tt>. Change <tt>innodb_buffer_pool_size</tt> to a smaller value, such as <tt>256M</tt>. You can also lower the other sizes accordingly. Sugested minimal configuration:
+To change settings for <tt>zends</tt>, edit <tt>/opt/zends/etc/zends.conf</tt>. Change <tt>innodb_buffer_pool_size</tt> to a smaller value, such as <tt>256M</tt>. You can also lower the other sizes accordingly. Suggested minimal configuration:
 <pre>

@@ Line 3: / Line 3: @@
 == ZenPacks ==
-There are large numbers of ZenPacks available for Zenoss, which are basically extensions to the core product that can be installed like plug-ins. The home for Zenoss ZenPacks is [[https://github.com/zenoss/ Zenoss' GitHub page]].
+There are large numbers of ZenPacks available for Zenoss, which are basically extensions to the core product that can be installed like plug-ins. The home for Zenoss ZenPacks is [https://github.com/zenoss/ Zenoss' GitHub page].
-One notable ZenPack is the [http://community.zenoss.org/blogs/zenossblog/2012/01/24/openvz-and-zenossOpenVZ ZenPack], written by Daniel Robbins :)
+One notable ZenPack is the [http://community.zenoss.org/blogs/zenossblog/2012/01/24/openvz-and-zenoss OpenVZ ZenPack], written by Daniel Robbins :)
 == Requirements ==

← Older revision		Revision as of 22:57, 13 February 2012
Line 1:		Line 1:
	Zenoss is an Open Source IT monitoring and management application. '''Zenoss Core''' is the name of the Open Source release, and the commercial version is called '''Zenoss Service Dynamics''', and includes additional functionality including impact management. [[user:Drobbins\|Daniel Robbins]] is part of the Zenoss team, so you are encouraged to give Zenoss a try if you enjoy Funtoo Linux :)		Zenoss is an Open Source IT monitoring and management application. '''Zenoss Core''' is the name of the Open Source release, and the commercial version is called '''Zenoss Service Dynamics''', and includes additional functionality including impact management. [[user:Drobbins\|Daniel Robbins]] is part of the Zenoss team, so you are encouraged to give Zenoss a try if you enjoy Funtoo Linux :)
		+
		+	== ZenPacks ==
		+
		+	There are large numbers of ZenPacks available for Zenoss, which are basically extensions to the core product that can be installed like plug-ins. The home for Zenoss ZenPacks is [[https://github.com/zenoss/ Zenoss' GitHub page]].
		+
		+	One notable ZenPack is the [http://community.zenoss.org/blogs/zenossblog/2012/01/24/openvz-and-zenossOpenVZ ZenPack], written by Daniel Robbins :)

	== Requirements ==		== Requirements ==

← Older revision		Revision as of 22:54, 13 February 2012
Line 117:		Line 117:

	This will cause zenoss to skip the commented-out daemons and only start the daemons you need. You can always come back to the <tt>daemons.txt</tt> file and modify it as necessary as you utilize more zenoss functionality.		This will cause zenoss to skip the commented-out daemons and only start the daemons you need. You can always come back to the <tt>daemons.txt</tt> file and modify it as necessary as you utilize more zenoss functionality.
		+
		+	[[Category:Featured]]
		+	[[Category:DevOps]]

← Older revision		Revision as of 22:53, 13 February 2012
Line 48:		Line 48:

	Type <tt>zeneventserver restart</tt> as the <tt>zenoss</tt> user to apply these new settings.		Type <tt>zeneventserver restart</tt> as the <tt>zenoss</tt> user to apply these new settings.
		+
		+	=== Stopping Daemons ===
		+
		+	Zenoss uses ZenPacks to extend functionality of the core product, and also includes some additional daemons that you may not need. To turn extra daemons off, perform the following steps:
		+
		+	<pre>
		+	# touch /opt/zenoss/etc/DAEMONS_TXT_ONLY
		+	</pre>
		+
		+	Then create a file called <tt>/opt/zenoss/etc/daemons.txt</tt> that contains something like this:
		+
		+	<pre>
		+	zeneventserver
		+	zeneventd
		+	zenwebserver
		+	zenhub
		+	zenjobs
		+	zenping
		+	zensyslog
		+	zenstatus
		+	zenactiond
		+	zentrap
		+	zenmodeler
		+	zenperfsnmp
		+	zencommand
		+	zenprocess
		+	zenrrdcached
		+	zenwin
		+	zeneventlog
		+	#zenjmx
		+	zenjserver
		+	zenwinperf
		+	zenmailtx
		+	zenwebtx
		+	#zenvmwareevents
		+	#zenvmwareperf
		+	#zenvmwaremodeler
		+	#zenucsevents
		+	#zenvcloud
		+	zenimpactserver
		+	zenimpactstate
		+	zenimpactgraph
		+	zenperfetl
		+	zenetl
		+	</pre>
		+
		+	The list above is a list of all daemons that start when you run <tt>zenoss restart</tt> as the <tt>zenoss</tt> user. I've commented out the ones I don't want by appending a <tt>#</tt>.
		+
		+	Now modify <tt>/opt/zenoss/bin/zenoss</tt> and change this part of the file:
		+
		+	<pre>
		+	if [ -f "$ZENHOME/etc/daemons.txt" ]
		+	then
		+	D=`cat $ZENHOME/etc/daemons.txt`
		+	C="$C $D"
		+	fi
		+	</pre>
		+
		+	...so that it looks like this...
		+
		+	<console>
		+	if [ -f "$ZENHOME/etc/daemons.txt" ]
		+	then
		+	D=`cat $ZENHOME/etc/daemons.txt##b## \| grep -v "^#"`
		+	C="$C $D"
		+	fi
		+	</console>
		+
		+	This will cause zenoss to skip the commented-out daemons and only start the daemons you need. You can always come back to the <tt>daemons.txt</tt> file and modify it as necessary as you utilize more zenoss functionality.

← Older revision		Revision as of 22:47, 13 February 2012
Line 38:		Line 38:
	# ##i##/etc/init.d/zends start		# ##i##/etc/init.d/zends start
	</console>		</console>
		+
		+	=== zeneventserver ===
		+
		+	Zeneventserver is a new Java-based event server for Zenoss and is written in Java. By default, it will allow the Java heap to get quite large. This can be modified by editing the <tt>/opt/zenoss/bin/zeneventserver</tt> script and appending an <tt>-Xmx512m</tt> option to the <tt>DEFAULT_ZEP_JVM_ARGS</tt> file, as follows:
		+
		+	<pre>
		+	DEFAULT_ZEP_JVM_ARGS=${DEFAULT_ZEP_JVM_ARGS:-"-server -Xmx512m"}
		+	</pre>
		+
		+	Type <tt>zeneventserver restart</tt> as the <tt>zenoss</tt> user to apply these new settings.