Integrating Scrutinizer with your SolarWinds install will add an additional layer of security to your network in two ways. But integrating Scrutinizer with your NMS will allow your organization access to them.
Historically, this depth of data could only be accessed with packet capture or network agents-details like jitter, packet loss, URL, and layer 7 application are all there. The problem? The collector is throwing away context! Scrutinizer reports on over 5000 unique elements within flow data. NetFlow v5) and only ‘report’ on those-everything else is tossed out with the bathwater. More often than not, ‘support’ means the vendor will parse out legacy flow fields (e.g. Here’s the rub: if you look at any product that collects flow data, you’ll see a particular phrase somewhere in the product description- “ Supports v5, v9, IPFIX, sFlow, J-Flow, etc.” If you’re new to flow technology, you may not realize that there is a key difference between ‘ supports’ and ‘ reports.’ After all, SolarWinds already collects flow data…right?īy integrating Scrutinizer with any large-scale network monitoring system, there are 3 key gains I often reference: context, security, and scale.
Before we get to the how of integration, we need to understand why we would want to do this in the first place. This blog will provide a detailed guide on how to integrate SolarWinds Orion with Plixer’s Scrutinizer.
0 kommentar(er)
