5 Replies Latest reply on Sep 23, 2009 5:53 PM by Donald_Francis

    new feature request  (well, 2 actually).

    timf

      1.  I would love to be able to create applications by ports and then by node IP address(s) or node names.    We have a lot of internal web based applications that I would like to create an app. group name for so they are listed separately  instead of just lumped all together under http.  Also, I have some non-web based apps that run over port 80 that I would like to separate from the http traffic.  For example, i have an imaging system that uses port 80 to transfer files.  I want netflow to look at the port and then source/destination server names and be able to report is as my imaging app instead of lumping it with http in the top xx applications.

       

      2.  Our DB server is getting maxed out.  I would love if the netflow database could reside on a different physical server than the NPM db.

        • Re: new feature request  (well, 2 actually).
          chris.lapoint

          1.  I would love to be able to create applications by ports and then by node IP address(s) or node names.    We have a lot of internal web based applications that I would like to create an app. group name for so they are listed separately  instead of just lumped all together under http.  Also, I have some non-web based apps that run over port 80 that I would like to separate from the http traffic.  For example, i have an imaging system that uses port 80 to transfer files.  I want netflow to look at the port and then source/destination server names and be able to report is as my imaging app instead of lumping it with http in the top xx applications.

          Good news here.  See this post: OLD - what we're working on

          2.  Our DB server is getting maxed out.  I would love if the netflow database could reside on a different physical server than the NPM db.

          We're looking at various options here longer-term. 

          In the interim, have you heard about our smart traffic optimization feature?  We've found based on several packet captures that 95% of the traffic volume may be represented in a little as 4% of flows.   This means if your primary use-case for traffic analysis is to get visibility into the Top talkers, you're storing a lot of unnecessary data in your database (impacting DB size and resource/report loading time).  You can enable smart traffic optimization and set it to 95%, which means that only those flows that represent 95% of total traffic volume on your network will be stored. 

          If you're interested in hearing more about this setting, please send me a private message and I'll walk you through it in more detail.

            • Re: new feature request  (well, 2 actually).
              timf

              That's great that my first feature request is on the roadmap at least.  Now the next question... ETA?

               

              Secondly, I  have already directly worked with your dev. team on the smart traffic feature.  We have done this in our configuration and it helped us tremendously.  Our netflow web response is faster than ever.  However, we still have many thousands of nodes in NPM and out db server is running hot.  The more load we can distribute to other SQL servers the better.

              And one last question..  What's the possibility of future support of the netflow database on a different server, AND, that different server be a MySQL box?  Or am I asking a bit too much now.  :) 

              Thanks again.