18 Replies Latest reply on Mar 18, 2009 9:19 AM by chris.lapoint

    My top 10 for the next release

      Here is my top 10 (okay, my top 11 in order) that I'd love to see in the next release of SolarWinds. That is if I controlled the world.


      1. One alert engine. Configure alerts for events, syslog, traps from one interface and have all alerts listed in one place.
      2. Connect to relationship between nodes, or interfaces and nodes. I want to know what is connected to a switch, so when the switch goes down I don't get alarms for every node connected to it.
      3. After database is created and an account is created to manage that database, then no more SA privileges needed for Database Manager, and software upgrades.
      4. Multiple elements on one graph. I'd like to graph more than one custom poller on a graph, or if I wanted to to see bandwidth and CPU util on one graph. Whatever, just give me the ability to graph more than one thing.
      5. Change columns in advance alerts. I want to see the alert message, and current value of the alerts. Not group advanced alerts, just list them. I hate that I can't un-group the advanced alerts.
      6. Ability to un-manage a node or interface from the web.
      7. The ability to edit multiple nodes, or interfaces at once. For example, if I need to change the SNMP community string on all nodes.
      8. Ability to gather statistics of an interface, but I don't care if it goes down, so don't alert on it. Ability to turn off alerting on interfaces.
      9. Don't just roll up node up or node down status in node icons, but also roll up node problems (CPU, volumes, alerts from traps, syslog, custom pollers).
      10. Auto-discovery abilities in NPM.
      11. LANSurveyor to use NPM database to make map. Don't want to discover my entire network multiple times.

        • Re: My top 10 for the next release
          aLTeReGo
          3. After database is created and an account is created to manage that database, then no more SA privileges needed for Database Manager, and software upgrades.


          Wasn't this addressed in 8.5?

          • Re: My top 10 for the next release
            BryanBecker
            I like this list and wanted to echo jds thoughts.  I was looking for #4 today and saw this post so I figured I'd also request it along these other ideas.

            BB
              • Re: My top 10 for the next release

                All of jds' items are definitely on my list. Another one I wanted to add was to have the new custom MIB poller use the polling engine's time to generate a time stamp, and not depend on the database to assign a timestamp when it gets written. Here's my problem:


                 Network Device, Poller, Orion Web Server - all on UTC


                Database (on a separate server cluster and managed by another group) - on local time.


                This leads to a device with custom MIB graphs showing a 5-6 hour gap in data. The canned graphs are all on the correct time.

              • Re: My top 10 for the next release
                pserwe

                I have to echo a strong need for item #1 in particular.  The separation of syslog, traps, and polls is a constant source of frustration. 

                The fact that I can't write an event to the NPM when I receive a particular type of trap or syslog, and then alert on it is majorly handicapping.

                Many devices in my network don't have great polling capabilities, yet they trap furiously when something is wrong.  So far, the most interesting thing I can do with traps or syslog is to blindly forward them along.  I need to be able to create alerts with detailed instructions in them for escalation and other instructions for the people they are going to.

                Item #2 is also high on the list.  Having dependencies is something supporting in opensource monitoring systems like Nagios or Zenoss to name two.

                Item #4 just makes sound sense, although my installation isn't developed enough to require it (yet).

                Item #7 is something I've been wanting since the first month I had Orion installed.  Mass editing of nodes, mass editing of users, mass editing of view limitations are all really important to me.  I'm currently using a functional workaround for view limitations, based on Custom Properties.

                Item #8 is critical.  I have all kinds of interfaces I want to gather statistics on, but not bother alerting.  Currently my only workaround is to ignore statistics gathering and leave them de-checked in the individual node properties, because I really don't need to know when a customer drops LAN ports on a IAD.

                Item #11 is also big, but since I've ignored the map, it doesn't bother me at the moment.

                Another one that's pretty big for me, would be the ability to have the Node Addition interface also allow me to put in custom properties based on whichever custom properties I have.  I can't tell you how many times I've forgotten to set the custom properties only to find out my alerts (which are all transitioning to being based in part off of custom properties) don't work.

                Peter

                 

                • Re: My top 10 for the next release

                  2) Agreed.  This is possible now in ipMonitor, and I'd like to see it cross over to Orion.

                  3) If you're going to make changes to a database (add fields, change schema, etc.) then I don't know how you'd do it without SA or at least some additional dbase privileges.

                  4) YES.  I would like to show each custom poller for a device in it's own column in Orion Reports.  This is currently not possible.

                  7) Cool!  Bulk change ability is a good idea.

                  10) I'd like auto-discovery of servers vendor and model.  HP, Dell, IBM.  I realize this will be somewhat hit and miss, because they change their server MIBS, but I can send you a list of OID's to poll to get a reasonable hit list.  The MIB's are already there.

                  I would like eventually to get a server inventory report out of Orion with something like the following:

                  Name | Brand | Model | Serial | Processor(number and/or type) | Memory(amount)

                  Drive info, BIOS Info, and NIC info are nice to have's.  I dug out the OID's for this info to put into custom pollers, then found I couldn't create a single report with each custom poller in it's own column.   Wah.

                    • Re: My top 10 for the next release
                      denny.lecompte

                      #3 has already been addressed since this original post.

                       

                      #7 already exists in the web console.  We put this in last july, in v9.0.

                       

                       

                      I would like eventually to get a server inventory report out of Orion with something like the following:

                      I don't see this happening in NPM.  Inventory is not a core monitoring function.  We will continue to add inventory functionality to Orion Network Configuration Manager, however.

                        • Re: My top 10 for the next release

                          Ah ha!!  Yes, this is what happens when I type of things I haven't checked out for myself. :)  Thanks, Denny!  I'll check out NCM and see what it can do for us.

                            • Re: My top 10 for the next release
                              denny.lecompte

                              Admittedly, I am a little biased, but NCM is a pretty awesome complement to NPM, and we intend to pull these two products into even closer orbits.

                                • Re: My top 10 for the next release
                                  gert

                                  is there a date planned for the next release, and will there be intergration with the workspace?

                                  • Re: My top 10 for the next release
                                    pserwe

                                    Unfortunately, NCM has some critical auth issues that kill it's functionality for more than feeding some relatively trivial information into Orion's interface.

                                    I need the ability to provision users just as I do in Orion or just preferably USE Orion users I already have and assign them all the necessary rights, including the ability (if I so choose) to allow them to log directly into a device via SSH or telnet proxied by the NPM or NCM server.  As it is, NCM is considerably less than useful, because it doesn't support AD auth, admin-defined user auth, or Orion auth. Tech support has been far less than useful in proxy for dev, and the whole thing has me considerably upset that I'm paying good money for software that for most everything that I actually want to use it for, is broken.  I was grateful to find that the NCM does actually respect the view limitations of NPM, that was a big plus.

                                    NCM Also has a critical lack of functionality in the security arena.  It *must* parse out the snmp strings, servers, and local users from the router configurations.  I understand, post-parsing the output of show run requires some regex skills and some really complicated programming language like perl, but it's still critical.  Sorry to thread-hijack, but I've spent 6 months getting nowhere with support on the autho issues, and while I love every new release of NCM as it integrates even tighter into NPM, there are several *crucial* things that seem to be getting ignored, or not moving fast enough for our investment to be more than paying for software we can't use effectively for what we need.

                                    Peter

                                      • Re: My top 10 for the next release
                                        chris.lapoint


                                        Unfortunately, NCM has some critical auth issues that kill it's functionality for more than feeding some relatively trivial information into Orion's interface.

                                        I need the ability to provision users just as I do in Orion or just preferably USE Orion users I already have and assign them all the necessary rights, including the ability (if I so choose) to allow them to log directly into a device via SSH or telnet proxied by the NPM or NCM server.  As it is, NCM is considerably less than useful, because it doesn't support AD auth, admin-defined user auth, or Orion auth. Tech support has been far less than useful in proxy for dev, and the whole thing has me considerably upset that I'm paying good money for software that for most everything that I actually want to use it for, is broken.  I was grateful to find that the NCM does actually respect the view limitations of NPM, that was a big plus.

                                        NCM Also has a critical lack of functionality in the security arena.  It *must* parse out the snmp strings, servers, and local users from the router configurations.  I understand, post-parsing the output of show run requires some regex skills and some really complicated programming language like perl, but it's still critical.  Sorry to thread-hijack, but I've spent 6 months getting nowhere with support on the autho issues, and while I love every new release of NCM as it integrates even tighter into NPM, there are several *crucial* things that seem to be getting ignored, or not moving fast enough for our investment to be more than paying for software we can't use effectively for what we need.

                                        Peter

                                         



                                        Peter, I've transferred your post to the NCM feature request forum: My Top 10 for the next release

                                        You'll find my response there.