Data visibility groups overview

Whereas server groups can limit what servers a user has access to, data visibility groups (DVGs) limit what data (events) a user has access to. For example, a DVG can be used to restrict a user to Accounting data on Server A and Server B.

DVGs are an optional building block that can be used to limit user access to:

• Data shown on the following monitors:
  • Completed Process Activity Monitor
  • Queued Process Activity Monitor
  • Active Alerts Monitor
  • Handled Alerts Monitor
• Alert counts shown on the Server Status Monitor
• Rule configuration
• SLC configuration

To set up data visibility groups, you can specify criteria for segmenting data as needed for your organization. For example, you could segment data into different lines of business (LOBs) or different functional areas, such as accounting or payroll. When events match on any criteria for a DVG, that data visibility name is put into the DVG attribute of the event. Therefore, the event is “tagged” with that DVG.

In addition, each DVG may have its own set of rules and SLCs associated with it, allowing a single event to be processed by multiple rules and SLCs, resulting in different actions.