Once you have created policies, apply a default for all maps, a policy for a particular map, or apply a policy at the device, interface, or dataset level.

Transcript

Once you've defined your retention policies, as described in part one of this video, you can apply these policies as needed.

Set the default retention policy for a server from the Retention Policies pane of the Server Settings window. As you can see, all of the default policies as well as the policies we created in part one are available. If you don't override it at the map device interface or data set level, the default policy is used. Set the default retention policy for a map from the Map Settings window. I'm setting this maps policy to the medium resolution policy I created in part one.

You can also set the default policy for a particular device or an interface. With the map editable and the device or interface selected, choose Set Data Retention from the Monitor menu, or from the Context menu set info sub menu. I'll set this one to the high resolution policy I created in part one.

Finally, you can set policies for individual data sets. With the map editable, switch to the Dataset View. Check the box next to a device in the list on the left. The kinds of data available from that device appear on the right. I'll set the policy for availability to Inherit so it uses the default I just set for my device. Certain data sets, including response time, short-term packet loss, and input and output byte rates for visible interfaces, are assigned to the auto record policy by default.

For built-in probes, Dartware has chosen data sets that seems sensible to record, and assign the auto record policy to them. If you develop your own probes, you can specify which data sets are included. Information on what gets recorded in built-in probes, and how to specify which data is recorded in custom probes is available in the developer guide. That's retention policies in a nutshell. For more information, see the user guide available from the Help menu.


Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: February 22, 2019