AD Architecture

This section details example Workbench Anomaly Detection (AD) architectures; both stand-alone and distributed Anomaly Detection (AD) deployments.

Important

• The Anomaly Detection components must be installed on separate hosts from the Workbench (WB) core components - i.e. do NOT install AD on the WB Hosts

AD Single Node - within single Workbench Data-Center

The example architecture below provides the following:

• Workbench AD is a single Node/Host
• Workbench AD is integrated with a single Workbench Data-Center/Site (i.e. APAC) deployment

AD Multi Node - within single Workbench Data-Center

The example architecture below provides the following:

• Workbench AD is a multi/HA Nodes/Hosts
• Workbench AD has Additional Nodes/Hosts and is therefore running AD in High Availability mode (i.e. redundancy) and Load Balancing (i.e. increased scalability) mode
• Workbench AD is integrated with a single Workbench Data-Center/Site (i.e. APAC) deployment

AD Single Node - within multi Workbench Data-Centers

The example architecture below provides the following:

• Workbench AD is a single Node/Host at each Data-Center
• Workbench AD is integrated with a multi Workbench Data-Center/Site (i.e. APAC and EMEA) deployment
• Given the multi Data-Center integration, Workbench Insights will be visible holistically irrespective of the Workbench Data-Center the user is logged into

AD Multi Node - within multi Workbench Data-Centers

The example architecture below provides the following:

• Workbench AD is a multi/HA Nodes/Hosts at each Data-Center
• Workbench AD has Additional Nodes and is therefore running in High Availability mode (i.e. redundancy) and Load Balancing (i.e. increased scalability) mode
• Workbench AD is integrated with a multi Workbench Data-Center/Site (i.e. APAC and EMEA) deployment
• Given the multi Data-Center integration, Workbench Insights will be visible holistically irrespective of the Workbench Data-Center the user is logged into