Take a look at the response below. By the way most of these new topics being launched detailing feature requests already have threads open in the Feature Request Topic.
In reference to number 1:
I realize that you are looking for something a bit more detailed but this should get your brain moving.
I have modified the 01-AllNodes.Resource file to display the device vendor type icon and also to order the list first by vendor and then by caption. You could just as easily use the SNMP location field to order devices. If you use defined location labelling schemes for SNMP this would allow you to order by location, vendor, and caption.
If you need assistance with this let me know. I have been ripping through the resource files ever since rix gave me the heads up. We now have a whole list of customizations running on the web interface that greatly improve the utility of the product.
<!-- Title=All Nodes -->
<!-- Advanced=FALSE -->
<!--#include Virtual=/NetPerfMon/scripts/NetPerfMon.asp -->
<!--#include Virtual=/NetPerfMon/scripts/Resource.asp -->
<%
Title="All Nodes"
HelpPage="AllNodes"
DoResourceHeader
Set SQLResource = NetPerfMon.NewSQLResource
SQLResource.SQL="Select NodeID,Caption,Nodes.GroupStatus,Nodes.VendorIcon From Nodes Order By Vendor,Caption"
SQLResource.Execute
%>
<table border="0" cellPadding="2" cellSpacing="0" width="100%">
<% Do While Not SQLResource.EOF %>
<tr>
<td class="Property" vAlign="center" width="20"><%=SQLResource.GetProperty("GroupStatus;SmallIcon")%> </td>
<td class="Property"><a href="https://thwack.solarwinds.com/NetPerfMon/View.asp?View=NodeDetails&NetObject=N:<%=SQLResource.GetProperty("NodeID")%>"><%=SQLResource.GetProperty("Caption")%></a> </td>
<td class="Property" vAlign="center" width="20"><%=SQLResource.GetProperty("VendorIcon")%></td>
</tr>
<%
SQLResource.MoveNext
Loop
%>
</table>
<br>
quote:
--------------------------------------------------------------------------------
Originally posted by rcouget
We are running Orion with approximately 30K elements sread across 2 front end pollers and 1 backend 4.6 GIG Enterprise SQL database. I have a few feature requests.
1. The ability to group elements on the Home page by folder as opposed to maps. We are a large ISP and the ability to group elements based on market, and type of CPE would be tremendously helpful.
2. Orion today will auto discover "NEW" elements of a node but will not start polling these automatically. We are provisioning daily on our routers and having to list elements and then do a select all on 40 nodes with up to a thousand interfaces per node. This is a tremendously time consuming task.
3. When an element for a node is deleted, the node shows up as unknown as opposed to auto deleting out of the database.
4. We need the ability to mark an element as not wanting to be polled. Today we have to go to the node, and delete elements we don't want to poll. It is to cumbersome to have to handle these in the current methodology.
5. We need to be able to not poll an entire group of interfaces based on type. I.E. we use ATM sub-interfaces, the router gives up an atm sub-if element and a aal5 element for every atm sub-interface creted for a customer. There is nothing informative about the sub-if of the 2, the aal5 has all the info about the sub-interface. This has added approximately 8000 elements that are being polled and do not need to be, adding a lot of overhead on the pollers.