<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Easy way to monitor Services]]></title><description><![CDATA[<p dir="auto">Is there an easy way to setup discovery (like with HDD for free space ect) on a node so the system will auto scan / check services, in an ideal world I would like the system to scan for all automatic services and add them, then the standard alerts if not running ect</p>
<p dir="auto">Thank you</p>
]]></description><link>https://forum.netxms.org/topic/5340/easy-way-to-monitor-services</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 13:10:22 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/5340.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 27 Nov 2017 08:21:45 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Easy way to monitor Services on Fri, 01 Apr 2022 15:45:18 GMT]]></title><description><![CDATA[<p dir="auto">i'm trying to do the exact same thing to make the dci creation process for services marked as 'auto start up' a less manual undertaking.  did you get anywhere with this?  if so some screenshots would be lovely to make my life easier!  thanks</p>
]]></description><link>https://forum.netxms.org/post/31173</link><guid isPermaLink="true">https://forum.netxms.org/post/31173</guid><dc:creator><![CDATA[dmna007]]></dc:creator><pubDate>Fri, 01 Apr 2022 15:45:18 GMT</pubDate></item><item><title><![CDATA[Reply to Easy way to monitor Services on Wed, 29 Nov 2017 12:18:17 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">Without providing a full guide (the Admin Guide, Wiki and Forum should be able to help with the details), you could use a PowerShell script to generate an ExternalList. Something like this:</p>
<pre><code>$wmiServiceNames = (Get-WmiObject Win32_Service -Filter "StartMode='Auto'").Name
foreach ($wmiServiceName in $wmiServiceNames) {
    $serviceDisplayName = (Get-Service $wmiServiceName).DisplayName
    $wmiServiceName + "," + $serviceDisplayName
}
</code></pre>
<p dir="auto">Note, the above will provide a list of Service Names and Service Display Names, separated by commas.<br />
That way you can use instance discovery to split the two, then use DCI the parameter</p>
<pre><code>System.ServiceState{instance}
</code></pre>
<p dir="auto">while being able to use the more readable {instance-name} for the DCI description.</p>
<p dir="auto">Going a step further, you can create an event, action and event processing rule to automatically attempt to restart a service should it not be running.</p>
<p dir="auto">Cheers</p>
]]></description><link>https://forum.netxms.org/post/23439</link><guid isPermaLink="true">https://forum.netxms.org/post/23439</guid><dc:creator><![CDATA[Tursiops]]></dc:creator><pubDate>Wed, 29 Nov 2017 12:18:17 GMT</pubDate></item><item><title><![CDATA[Reply to Easy way to monitor Services on Mon, 27 Nov 2017 10:47:18 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">most likely instance discovery for DCI creation should help (maybe with script a s a source).</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/23432</link><guid isPermaLink="true">https://forum.netxms.org/post/23432</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Mon, 27 Nov 2017 10:47:18 GMT</pubDate></item></channel></rss>