Content in THWACK/place-content.jspa?filterID=contentstatus[published]~objecttype~objecttype[idea]&containerType=14&containerID=2131&targetUser=-1
Recent content in THWACKenWed, 04 Jul 2012 15:31:40 GMTJive Engage 9.0.3.0 (http://jivesoftware.com/products/)2012-07-04T15:31:40ZenIf...Then...Else statements for Alert Managerhttps://thwack.solarwinds.com/ideas/1110
<!-- [DocumentBodyStart:e7524836-9ca9-4224-b2d6-1e7e86c39c59] --><div class="jive-rendered-content"><p>I think it would make managing alerts much easier if we were able to build an if-then-else statement into the actions for an alert.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>My example...</p><p>I create an alert for a particular set of criteria, but I want to enable a different response depending on who is responsible for solving the issue.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>IF Node.Owner = "Server" THEN do(Action1)</p><p>IF Node.Owner = "Network" THEN do(Action2)</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>I gather it would be fairly complicated to implement, but I think it would really improve the alert manager.</p></div><!-- [DocumentBodyEnd:e7524836-9ca9-4224-b2d6-1e7e86c39c59] -->Wed, 04 Jul 2012 15:31:40 GMTcommunityteam@solarwinds.comhttps://thwack.solarwinds.com/ideas/11102012-07-04T15:31:40Z6 years 9 months ago0Undeleting an element (node/interface/volume etc.)https://thwack.solarwinds.com/ideas/1070
<!-- [DocumentBodyStart:71bb5cd2-ec11-4140-a2a3-d27737adfdac] --><div class="jive-rendered-content"><p>A few minutes ago I accidentally deleted my backbone switch (and all the interfaces of course). Since undeleting an element (node, interface etc.) is not possible (Except restoring SQL from backup) it means that I've lost all the interface statistics, node statistics (CPU, Memory, Availability) and atlas map drawing. And this is not my first time. This is a common issue for all of us. If NPM can remember an element for a specific period of time that would be great. I think It shouldn't be that hard to implement this.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="font-size: 12px; font-family: Arial, sans-serif; color: #000000; background-color: #ffffff;"><span style="font-style: inherit; font-family: inherit;"><strong>PS; Please vote these ideas also if you like them of course. And I bet you do. <span aria-label="Happy" class="emoticon_happy emoticon-inline" style="height:16px;width:16px;"></span></strong></span></p><p style="min-height: 8pt; padding: 0px;">&#160;</p><ul><li><span style="font-style: inherit; font-family: inherit;"><a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1246" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1246" style="font-style: inherit; font-family: inherit; color: #13b4dc;">Granular node management rights</a></span></li><li><span style="font-style: inherit; font-family: inherit;"><a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1656" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1656" style="font-style: inherit; font-family: inherit; color: #13b4dc;">Multiple IP <span style="font-style: inherit; font-family: inherit; text-decoration: underline;">Polling</span> support for a single node</a></span></li><li><a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1501" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1501" style="font-style: inherit; font-family: inherit; color: #13b4dc;">Orion Next Generation User Interface</a></li><li><a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1070" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1070" style="font-style: inherit; font-family: inherit; color: #13b4dc;">Undeleting a node/interface should be possible</a></li><li><a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1271" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1271" style="font-style: inherit; font-family: inherit; color: #13b4dc;">Custom property support for groups</a></li></ul></div><!-- [DocumentBodyEnd:71bb5cd2-ec11-4140-a2a3-d27737adfdac] -->Sun, 26 Jan 2014 07:03:08 GMTcommunityteam@solarwinds.comhttps://thwack.solarwinds.com/ideas/10702014-01-26T07:03:08Z5 years 2 months ago0Orion Dark Theme Optionhttps://thwack.solarwinds.com/ideas/8037
<!-- [DocumentBodyStart:f657aa9f-7ac5-47bb-8ec1-0c3e3f1e2ef8] --><div class="jive-rendered-content"><p>Please provide the option to switch the website into a "Dark Theme"</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>Not only is this an often preferred experience for users, but it is a very standard practice in most NOC environments where the overhead lights are generally dim (think Mission Control)</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>Ideas:</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p><a href="https://thwack.solarwinds.com/servlet/JiveServlet/showImage/165490/dark-theme-1.png"><img alt="dark-theme-1.png" class="image-1 jive-image" height="342" src="https://thwack.solarwinds.com/servlet/JiveServlet/downloadImage/165490/dark-theme-1.png" style="width: 620px; height: 331px;" width="640"/></a></p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p><a href="https://thwack.solarwinds.com/servlet/JiveServlet/showImage/165491/WB0J69TPB.png"><img alt="WB0J69TPB.png" class="image-2 jive-image" height="375" src="https://thwack.solarwinds.com/servlet/JiveServlet/downloadImage/165491/WB0J69TPB.png" style="height: auto;" width="600"/></a></p></div><!-- [DocumentBodyEnd:f657aa9f-7ac5-47bb-8ec1-0c3e3f1e2ef8] -->Thu, 28 Dec 2017 19:59:47 GMTcommunityteam@solarwinds.comhttps://thwack.solarwinds.com/ideas/80372017-12-28T19:59:47Z1 year 3 months ago0Test/Development Licenseshttps://thwack.solarwinds.com/ideas/1145
<!-- [DocumentBodyStart:75980385-e555-4d00-a5c5-60410dddc2e4] --><div class="jive-rendered-content"><p><em><strong>Disclaimer: I know that there are other threads on this but I wanted to update it in this new Idea space.</strong></em></p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>I would really like to have Test/Development licenses for SolarWinds products, at least for the products that we have purchased.&#160; These licenses could be restricted to just a few nodes (like 10ish).</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>The reasons for this would be having the ability to do the following things in a non-production environment...</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><ul><li>Testing upgrades</li><li>Testing different configurations</li><li>Learning the SolarWinds products for SCP (SolarWinds Certified Professionals)<ul><li>In the case of SCP's I think they should get access to test licenses for all of the SW products to keep current</li></ul></li><li>Creating a small training environment</li><li>Creating a demo environment</li></ul><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>I am sure there are other reasons that I have not already thought of, please share if you have them and vote on this idea if you like it!</p></div><!-- [DocumentBodyEnd:75980385-e555-4d00-a5c5-60410dddc2e4] -->Fri, 08 Mar 2019 23:06:02 GMTcommunityteam@solarwinds.comhttps://thwack.solarwinds.com/ideas/11452019-03-08T23:06:02Z1 week 6 days ago0Granular Node Management Rights.https://thwack.solarwinds.com/ideas/1246
<!-- [DocumentBodyStart:6c1090f4-4ce7-4a3d-82f5-0f57300507a8] --><div class="jive-rendered-content"><p>There needs to be a simple way to assign users specific node management rights. For example, i have a group of users that i only want to be able to unmanage nodes, nothing more. There may be sophisticated ways of achieving this but it would be nice to have it built into the "Manage Accounts" section.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>Thanks for considering this.</p></div><!-- [DocumentBodyEnd:6c1090f4-4ce7-4a3d-82f5-0f57300507a8] -->Thu, 16 Aug 2012 08:57:02 GMTcommunityteam@solarwinds.comhttps://thwack.solarwinds.com/ideas/12462012-08-16T08:57:02Z6 years 7 months ago0EIGRP supporthttps://thwack.solarwinds.com/ideas/2227
<!-- [DocumentBodyStart:f8bd793f-5648-4674-9cec-66a81d7b1c84] --><div class="jive-rendered-content"><p>EIGRP<br/>Support EIGRP for routing neighbors/changes.</p></div><!-- [DocumentBodyEnd:f8bd793f-5648-4674-9cec-66a81d7b1c84] -->Wed, 29 May 2013 14:15:42 GMTcommunityteam@solarwinds.comhttps://thwack.solarwinds.com/ideas/22272013-05-29T14:15:42Z5 years 10 months ago0Unmanage reason (like shutdown tracker in Windows 2008)https://thwack.solarwinds.com/ideas/1018
<!-- [DocumentBodyStart:fca2b223-1657-42eb-b70c-2f952d40a09a] --><div class="jive-rendered-content"><p style="font-size: 12px; font-family: Arial, sans-serif; color: #333333; background-color: #ffffff;">I don't want anybody to use <strong>unmanage for no reason.</strong> Because that's what they are doing for almost every <strong>down</strong> node! And I have to ask everytime why did hey do it? Then I decided to create a custom property called "<strong>Unmanage reason" </strong>(name can be different). But because it is not mandatory they always forget (or intentionally) to fill it. So it should be impossible to unmanage a node without filling the unmanage reason at least which should pops up when anyone click the Unmanage button.</p><p style="min-height: 8pt; padding: 0px; font-size: 12px; font-family: Arial, sans-serif; color: #333333; background-color: #ffffff;">&#160;</p><p style="font-size: 12px; font-family: Arial, sans-serif; color: #333333; background-color: #ffffff;">These features also should be implemented along with it.</p><ul><li>There is no way to extend the unmanage time via NPM Web Console. It can be changed with SQL Query Update. But it is not flexible.</li><li>Unmanage date should be visible on the node details page. I can only see it via reports. (Partially implemented on NPM 10.6 Beta 2)</li></ul><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="font-size: 12px; font-family: Arial, sans-serif; color: #000000; background-color: #ffffff;"><span style="font-style: inherit; font-family: inherit;"><strong>Also the most needed features in NPM are below (IMHO)</strong></span></p><p style="min-height: 8pt; padding: 0px;">&#160;</p><ul><li><span style="font-size: 14pt; font-style: inherit; font-family: inherit;"><strong><a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1246" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1246" style="font-weight: inherit; font-style: inherit; font-family: inherit; color: #13b4dc;">Granular node management rights</a></strong></span></li><li><a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1703" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1703">False reboot alerts due to SNMP service restart &amp; Proper uptime information OoB<br/></a></li><li><span style="font-style: inherit; font-family: inherit;"><a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1656" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1656">Multiple IP <span style="font-weight: inherit; font-style: inherit; font-family: inherit; text-decoration: underline;">Polling</span> support for a single node</a></span></li><li><a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1501" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1501" style="font-style: inherit; font-family: inherit; color: #13b4dc;">Orion Next Generation User Interface</a></li><li><a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1070" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1070">Undeleting a node/interface should be possible</a></li><li><a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1271" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1271">Custom property support for groups</a></li><li><a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1317" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1317">Network Atlas Enhancements</a></li></ul><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="font-size: 12px; font-family: Arial, sans-serif; color: #000000; background-color: #ffffff;">Please vote those ideas as well if you think you need them.</p></div><!-- [DocumentBodyEnd:fca2b223-1657-42eb-b70c-2f952d40a09a] -->Fri, 05 Jan 2018 21:01:53 GMTcommunityteam@solarwinds.comhttps://thwack.solarwinds.com/ideas/10182018-01-05T21:01:53Z1 year 2 months ago0Calendar’s for maintenance windows, SLA’s, and production monitoring windowshttps://thwack.solarwinds.com/ideas/2655
<!-- [DocumentBodyStart:f8c90c4e-e90e-48d8-951a-ef2df4d34e69] --><div class="jive-rendered-content"><p>Calendar&#8217;s for maintenance windows, SLA&#8217;s, and production monitoring windows</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>I know this has been beatup before but I am attempting to introduce this at the product core level to be available to all components</p><p>in order to increase product capacility, flexibility, and scalability.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>Many shops these days varied production hours of operation, 24x7 schedules, maintenance windows and other recurring time periods where monitoring,&#160; alerting, or the absence of applies.&#160; The ability to define a schedule or calendar for various time periods is very helpful.&#160; This calendar can then be applied to a monitor, an alert, a view, or even a report.&#160; By doing so will reduce the number of alerts required to cover windows that vary over the period of a week.</p><p>In our environment, for example, we have a series of component monitors and alerts for two servers that monitor for existence of a process or service, MSMQ queue depth, log file update times, etc.&#160; The challenge is that on Monday &#8211; Friday from 0200 &#8211; 0600 they are in a maintenance window so alerts should not happen.&#160; To further compound this, the window changes on Saturday and again on Sunday to 0200 &#8211; 0700 and 0200 &#8211; 0800 respectively.&#160; Now our alert count goes way up to compensate.&#160; If the window changes due to business requirements we have to go in and touch a number of resources to adjust allowing for more opportunity to miss something.&#160; To further exacerbate the situation, there are<br/>other servers running related services also affected by this schedule.</p><p>So to have one schedule or calendar to define this window but able to be referenced by all of these aspects of the product makes it much easier to set up and maintain.&#160; This results in fewer configuration points to have to touch when making updates therefore reducing chances for errors.&#160; You can set up many different calendars for servers, interfaces, services, processes, monitors, alerts, etc.&#160; This extends the capability of the product a great deal and makes it more scalable and flexible.&#160; </p><p>This schedule also needs to be recurring in nature and as a core component available to all of the components of Solarwinds (NPM, SAM, WPM, Alerts, etc.)</p><p>Alert Central is not an option for us being it is a pre-rolled VM environment which goes against corporate policy by not being a company standard image.&#160; Therefore it will never be installed here.</p><p>The functionality I speak of here is related to what I have seen in Telalert 6e and works very well.&#160; In fact you can call from the command line the tool to see if a calendar is in effect to make use of it externally.</p></div><!-- [DocumentBodyEnd:f8c90c4e-e90e-48d8-951a-ef2df4d34e69] -->Tue, 20 Aug 2013 08:28:05 GMTcommunityteam@solarwinds.comhttps://thwack.solarwinds.com/ideas/26552013-08-20T08:28:05Z5 years 7 months ago0Multiple IP Address polling support for a single nodehttps://thwack.solarwinds.com/ideas/1656
<!-- [DocumentBodyStart:32895e75-4c7a-43bf-850a-be7eaa6cc4db] --><div class="jive-rendered-content"><p>It is taken from a feature request from <span style="; padding-right: 3px; color: #13b4dc; font-style: inherit; font-size: 1.1em; background-color: #ffffff; font-family: inherit; font-weight: inherit;"><strong>Questionario</strong></span>. By the way we need this badly.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p><a class="jive-link-message-small" data-containerId="2131" data-containerType="14" data-objectId="171757" data-objectType="2" href="https://thwack.solarwinds.com/message/171757#171757">Re: Feature Request: Multiple IPs per Node</a></p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="font-size: 12px; font-family: Arial, sans-serif; color: #000000; background-color: #ffffff;">Hi, right now I have several nodes double and triple for monitoring purposes.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="font-size: 12px; font-family: Arial, sans-serif; color: #000000; background-color: #ffffff;">One would be the standard Management VLAN IP, another for OSPF and another for a backup tunnel (which is constantly up)</p><p style="font-size: 12px; font-family: Arial, sans-serif; color: #000000; background-color: #ffffff;">now the management IP is reachable as long as one of these still work but I want to be notified if either of them goes down as well.</p><p style="font-size: 12px; font-family: Arial, sans-serif; color: #000000; background-color: #ffffff;">I dont need to get performance reports about each single IP but still get notifications if the IP on the node is unreachable!</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p style="font-size: 12px; font-family: Arial, sans-serif; color: #000000; background-color: #ffffff;">So it would be a nice enhancement to simply add more "secondary" IPs to nodes without having to create another object (Its not about the licenses but about the manageability).</p></div><!-- [DocumentBodyEnd:32895e75-4c7a-43bf-850a-be7eaa6cc4db] -->Fri, 14 Feb 2014 05:18:09 GMTcommunityteam@solarwinds.comhttps://thwack.solarwinds.com/ideas/16562014-02-14T05:18:09Z5 years 1 month ago0Silence Alerts While Still Monitoringhttps://thwack.solarwinds.com/ideas/1056
<!-- [DocumentBodyStart:d652a4b1-9302-4c04-a431-b7669f5bfe7f] --><div class="jive-rendered-content"><p>Posting this in NPM but the same would go for SAM applications.&#160; There should be a way from the web UI to put an element in a "maintenance mode" in which the node is monitored but no alerts would go out.&#160; Another user <a class="jive-link-profile-small jiveTT-hover-user" data-containerId="-1" data-containerType="-1" data-objectId="55597" data-objectType="3" href="https://thwack.solarwinds.com/people/adatole">adatole</a> developed a way to do this but I think it could be expanded upon (here is the original thread&#160; <a class="jive-link-thread-small" data-containerId="2017" data-containerType="14" data-objectId="41779" data-objectType="1" href="https://thwack.solarwinds.com/thread/41779">http://thwack.solarwinds.com/thread/41779</a> ).&#160; He referred to the concept as muting.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>There are many times where this may be necessary.&#160; Let's say WAN routers for example, we receive dozens of notices from carriers saying that a circuit will be down for maintenance for 5 minutes between 12AM - 6AM.&#160; I don't want to unmanage the device and lose all of that information for what typically is short duration outage.&#160; I do on the other hand want to silence any alerts that may come up during that period.</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>For this idea to be truly effective I believe the following components must be included</p><p style="min-height: 8pt; padding: 0px;">&#160;</p><p>1.&#160; The ability to put a Node/Interface/Volume/Application/Component in maintenance mode for a specific duration of time (just like we have for unmanaging)</p><p>2.&#160; The ability to schedule a recurring task for this mode (just like the unmanage schedule utility)</p><p>3.&#160; There should be a required note field that must be filled in by the user stating a reason for the maintenance mode</p><p>4.&#160; Would need more granular rights to allow a user to put a device in this mode without giving full node management rights.</p><p>5.&#160; Audit tracking of who made the changes similar to this idea (<a class="jive-link-idea" data-containerId="2131" data-containerType="14" data-objectId="1034" data-objectType="3227383" href="https://thwack.solarwinds.com/ideas/1034">http://thwack.solarwinds.com/ideas/1034</a>)</p><p>6.&#160; The maintenance period should not be taken into account in availability reports.</p></div><!-- [DocumentBodyEnd:d652a4b1-9302-4c04-a431-b7669f5bfe7f] -->Fri, 17 Mar 2017 16:10:40 GMTcommunityteam@solarwinds.comhttps://thwack.solarwinds.com/ideas/10562017-03-17T16:10:40Z2 years 4 days ago0