<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Server disk space monitoring with Kaseya</title>
	<atom:link href="http://www.tullibo.com/2010/03/01/server-disk-space-monitoring-with-kaseya/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tullibo.com/2010/03/01/server-disk-space-monitoring-with-kaseya/</link>
	<description>Kaseya, Automation &#38; other MSP stuff</description>
	<lastBuildDate>Tue, 11 Jan 2011 01:34:20 +1000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: tullibo</title>
		<link>http://www.tullibo.com/2010/03/01/server-disk-space-monitoring-with-kaseya/#comment-75</link>
		<dc:creator>tullibo</dc:creator>
		<pubDate>Sat, 05 Jun 2010 20:05:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.tullibo.com/?p=461#comment-75</guid>
		<description>Hi marc&lt;br&gt;&lt;br&gt;I tend not to use the trending features and instead look at weekly report of disk usage across all servers on one single report. IMO much less time consuming than dealing with individual trending alerts. I figure if you&#039;re going to use trending to alert then you my as well just alert.&lt;br&gt;&lt;br&gt;My rearm time on servers is usually 24 hours for alerts.</description>
		<content:encoded><![CDATA[<p>Hi marc</p>
<p>I tend not to use the trending features and instead look at weekly report of disk usage across all servers on one single report. IMO much less time consuming than dealing with individual trending alerts. I figure if you&#39;re going to use trending to alert then you my as well just alert.</p>
<p>My rearm time on servers is usually 24 hours for alerts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc</title>
		<link>http://www.tullibo.com/2010/03/01/server-disk-space-monitoring-with-kaseya/#comment-74</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Thu, 03 Jun 2010 05:26:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.tullibo.com/?p=461#comment-74</guid>
		<description>What did you enter for warning %, Trend Activated, Trending Window, Re-Arm Trending and any other setting?</description>
		<content:encoded><![CDATA[<p>What did you enter for warning %, Trend Activated, Trending Window, Re-Arm Trending and any other setting?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tullibo</title>
		<link>http://www.tullibo.com/2010/03/01/server-disk-space-monitoring-with-kaseya/#comment-64</link>
		<dc:creator>tullibo</dc:creator>
		<pubDate>Wed, 03 Mar 2010 02:31:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.tullibo.com/?p=461#comment-64</guid>
		<description>@michaelbgray - disagree entirely with using snmp to monitor disk space...in my mind, if you need to stack two systems on top of each other to get one system working then the first system simply isnt working properly!&lt;br&gt;&lt;br&gt;K disk monitoring definitely has its foibles and shortcomings but between using the inbuilt disk alerts and monsets and if you really need a third fallback, event log monitoring for low disk alerts, I think all bases are covered. The weakness would probably more lie in getting a helpdesker or NOC staffer to respond quickly enough to the low disk alert that it does not become so critical as to cause a real server problem.&lt;br&gt;&lt;br&gt;I haven&#039;t played extensively with snmp in K2 but I still think snmp in kaseya has a long way to go, granted something is better than nothing though</description>
		<content:encoded><![CDATA[<p>@michaelbgray &#8211; disagree entirely with using snmp to monitor disk space&#8230;in my mind, if you need to stack two systems on top of each other to get one system working then the first system simply isnt working properly!</p>
<p>K disk monitoring definitely has its foibles and shortcomings but between using the inbuilt disk alerts and monsets and if you really need a third fallback, event log monitoring for low disk alerts, I think all bases are covered. The weakness would probably more lie in getting a helpdesker or NOC staffer to respond quickly enough to the low disk alert that it does not become so critical as to cause a real server problem.</p>
<p>I haven&#39;t played extensively with snmp in K2 but I still think snmp in kaseya has a long way to go, granted something is better than nothing though</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: michaelbgray</title>
		<link>http://www.tullibo.com/2010/03/01/server-disk-space-monitoring-with-kaseya/#comment-62</link>
		<dc:creator>michaelbgray</dc:creator>
		<pubDate>Tue, 02 Mar 2010 05:37:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.tullibo.com/?p=461#comment-62</guid>
		<description>We dont use disk space monitoring for servers in Kaseya because of the reasons you mention above.  If I were going to do it, I&#039;d probably poll it with SNMP.  Have you given that a shot?</description>
		<content:encoded><![CDATA[<p>We dont use disk space monitoring for servers in Kaseya because of the reasons you mention above.  If I were going to do it, I&#39;d probably poll it with SNMP.  Have you given that a shot?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

