- Other than troubleshooting, how do you make use of your flow data?
- I produce a few reports that are delivered weekly to Network Engineers and Analysts. One set is edge/WAN and the other is Core. With aproximately 470 offices data access is a constantly evaluated cost. Our QoS engineers use the core data to justify policies configurations.
- How often do you look at flow data summaries, and in what form (on-demand via HTML form, automated reporting, CLI top-talkers, etc.)?
- It seems like every day flows are referenced or sighted. I personally don't consume the data, so I don't look at them as often. Primarily flow data is accessed through the Web UI. There are several reports we've developed that are automed delivey.
- Summaries have the side effect of masking more granular data, i.e. smaller flows that might be interesting. In your view, is this a concern, and if so, how do you work around it?
- This hasn't been a concern to date. As mentioned, a great deal of our flow data is consumed in summary format.
- How old does flow data have to get before it's no longer useful? For the sake of SQL, I was only keeping 7 days worth of flow data in NTA, assuming that it would be very unlikely I'd need to go back further than that. That was true most of the time, but there were times I wished I could dig back further.
- I have been keeping 30 days of compressed data for the traffic overview/profile reports.
↧
Re: How Do You Make The Most Of Your Flow Data?
↧