5 Replies Latest reply on Mar 9, 2010 5:22 PM by dclick

    Calling all feature requests

    chris.lapoint

      v9 is barely out the door and in addition to an upcoming service release, we're already gathering requirements for our next feature release of ipMonitor!  I've listed several of the core focus areas for us below (based on our prioritization) to help frame your requests.  


      1. Monitor Support
      2. User Interface
      3. Reporting
      4. Community Integration


      Now is the time to submit your top 5 requests in each area!   Feel free suggest other focus areas.


      Thanks,


      -Chris

        • Re: Calling all feature requests
          bleearg13

          One thing I've always felt ipMonitor should have is a single-monitor license or perhaps a client app that can be run on a remote machine which will test the availability of your ipMonitor server. This is a nice failsafe option in the event your ipMonitor server dies unexpectedly or loses connectivity.  The client app and the full install could basically monitor each other.

          Another user mentioned RDP monitoring, which is a great idea, too.

          Not sure how you could do any sort of community integration.  What are SW's ideas regarding this?

            • Re: Calling all feature requests
              chris.lapoint

              One thing I've always felt ipMonitor should have is a single-monitor license or perhaps a client app that can be run on a remote machine which will test the availability of your ipMonitor server. This is a nice failsafe option in the event your ipMonitor server dies unexpectedly or loses connectivity.  The client app and the full install could basically monitor each other.
               

              This is a really interesting idea.   I'll add this to the list for the next version.

              Another user mentioned RDP monitoring, which is a great idea, too.
               

              Can you elaborate further on what you'd expect to see around RDP monitoring?  

              Not sure how you could do any sort of community integration.  What are SW's ideas regarding this?
               

              Here are some of our ideas....would love to get your thoughts on these and if there are others that you'd suggest. 

               

              • Provide ability to import to and export device templates from Thwack
              • Provide ability to import to and export SmartGroups from Thwack
              • Create custom HTML resource in support of Thwack
              • Create tab for Thwack in product
                • Re: Calling all feature requests
                  bleearg13
                  Another user mentioned RDP monitoring, which is a great idea, too.
                   

                  Can you elaborate further on what you'd expect to see around RDP monitoring? 



                  That's a pretty good question.  Maybe there is some type of login that it can to which will ensure that RDP is responding.  Currently, we only monitor the availability of the TCP port, which is not always accurate - similar to how HTTP can be up, but not serving any pages.  Maybe the user who posted the original request has some other ideas.