How does NPM manage data retention for performance, trap, and flow data, and what considerations drive retention policy?

How does NPM manage data retention for performance, trap, and flow data, and what considerations drive retention policy?

• A. Retention policies govern how long performance, netflow, and trap data are kept
• B. Data is retained indefinitely by default
• C. Retention only affects event logs
• D. Retention policies are not configurable

Answer: (A)

Retention in NPM is about how long data lives. Retention policies determine how long performance data, NetFlow/flow data, and trap data are kept. Because each data type generates different volumes and has varying usefulness as it ages, NPM lets you set separate retention periods for each one. You might keep high-resolution performance data for a shorter window, roll up or archive older data, and apply different retention to traps or flows based on importance and volume. The policy decisions are driven by storage capacity and how it impacts performance, how long analysts need to review historical data, and any regulatory or business requirements for keeping data. The goal is to balance having enough history for meaningful analysis with keeping the system fast and affordable. So, retention policies govern how long performance, NetFlow, and trap data are kept and are configurable to fit your needs.

Retention in NPM is about how long data lives. Retention policies determine how long performance data, NetFlow/flow data, and trap data are kept. Because each data type generates different volumes and has varying usefulness as it ages, NPM lets you set separate retention periods for each one. You might keep high-resolution performance data for a shorter window, roll up or archive older data, and apply different retention to traps or flows based on importance and volume.

The policy decisions are driven by storage capacity and how it impacts performance, how long analysts need to review historical data, and any regulatory or business requirements for keeping data. The goal is to balance having enough history for meaningful analysis with keeping the system fast and affordable. So, retention policies govern how long performance, NetFlow, and trap data are kept and are configurable to fit your needs.