2 Replies Latest reply on Aug 19, 2014 8:35 AM by mharvey

    Scalability issues with Views

    multipl3x

      I am running into some problems with Views.
      I rely heavily on graphing as a troubleshooting tool. The only graph I have found that is helpful for instant troubleshooting ( loss of link bandwidth, for example ) is the multiple object chart.

       

      The problem is that the views do not scale well when using this. I can create a view, say for my 7600 routers and assign it as the default view for that device type, containing the multiple object chart. However, when I go to add critical interfaces to that chart, I have to add them manually, one by one, grouping them all into the same chart. Furthermore, searching for the interface is tedious, as in the below screenshot if my interface descriptions do not contain the search term I will not find them

       

       

      If I try to be less granular and just search for the node I cannot as it simply tells me I have a plethora of devices and will not allow me to view a full list:

       

       

      I would think that an individual view, with an individual multiple object graph per view would be the scalable solution here, but I cannot figure out how to do this. If this is not supported at this time please let me know and I will look into submitting a feature request. This is not going to work for me as is. Thanks for your time.

        • Re: Scalability issues with Views
          multipl3x

          Bump. Any ideas here?

            • Re: Scalability issues with Views
              mharvey

              The chart resource is ambiguous to the view it is on, I think here is where the overall problem lies.  When you are editing the resource, it will allow you to search the entire database as at that point it's not looking at the node you are looking at in your view.  While it's a tedious task to add them in, that is, from my experience, how it is designed.  One option that might help is creating custom properties on your interfaces and nodes, that you could then use as search criteria to help find what you are looking to add faster.

               

              Regards,

              Matthew Harvey

              Loop 1 Systems