Related
Recommended

what we are working on for NTA after v3.11

jacob_beucler
Less than one minute read time

Hello!

After the release of NTA 3.11 we here at SolarWinds turn our focus on performance and retention with in NTA. There have been several surveys that you all have been great about providing feedback on in addition to here on Thwack. Survey Says: make it run faster! Retain my data longer! You asked, we listened and now we are focused on delivering our next release with these enhancements as the primary focus.

  • Performance:
    • Decreasing Web Page Load Times
    • Decreasing Flow Processing overhead
    • Increasing Flow Processing speed and capacity
    • Decreasing SQL DB overhead
  • Retention:
    • No more data aggregation
    • Greatly increased detailed data retention

And for all you Juniper folks, we're also planning on supporting sampled jFlow. Stay tuned for more updates about beta builds in the near future! Can't be contained in 4.0

Disclaimer: This is not a commitment to a time frame or delivery of any of the features discussed below. This is also not a commitment to deliver all of these features in our next release. This post is intended to give you a rough idea of what we're doing.

  • :-)

    The NTA 4.0 situation should be similar to v3.11, as far as sampled flow processing:

    - sflow should work (sflow is by nature sampled)

    - sampled jflow should work, but we know that we have some issues with some devices (e.g. JunOS versions) that export flows without specifying that it is being sampled (so NTA processes those flows as unsampled ones=wrong stats).

    Whatever your case maybe, if you encounter an issue in this area, we need a pcap, because these are usually NTA "not understanding" how the routers is telling us whether the traffic is sampled or not.

    You can contact me directly with pcaps.

    We are actively working on this (the "What Are we Working" blog post will be revised shortly now that NTA 4.0 is released)

  • The NTA 4.0 situation should be similar to v3.11, as far as sampled flow processing:

    - sflow should work (sflow is by nature sampled)

    - sampled jflow should work, but we know that we have some issues with some devices (e.g. JunOS versions) that export flows without specifying that it is being sampled (so NTA processes those flows as unsampled ones=wrong stats).

    Whatever your case maybe, if you encounter an issue in this area, we need a pcap, because these are usually NTA "not understanding" how the routers is telling us whether the traffic is sampled or not.

    You can contact me directly with pcaps.

    We are actively working on this (the "What Are we Working" blog post will be revised shortly now that NTA 4.0 is released)

  • Can you confirm that the performance issue that you reported above is improved by 4.0?

    Also, any input on the missing features would help.

    Thanks wluther

  • fcaron yes, we have been testing it since it opened.  Still lacks several features to make it more usable/valuable to us, but overall, we have not had any issues with RC2.

Thwack - Symbolize TM, R, and C

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification Media Vault Link Accounts
About THWACK Blogs For Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2024 SolarWinds Worldwide, LLC. All Rights Reserved.