User Guide Functional Overview Requirements Architecture System Installation NetEye Additional Components Installation Setup The neteye Command Director NetEye Self Monitoring Tornado Business Service Monitoring IT Operation Analytics - Telemetry Geo Maps NagVis Audit Log Shutdown Manager Reporting ntopng Visual Monitoring with Alyvix Elastic Stack IT Operations (Command Orchestrator) Asset Management Service Level Management Cyber Threat Intelligence - SATAYO NetEye Update & Upgrade How To NetEye Extension Packs Troubleshooting Security Policy Glossary
module icon Visual Monitoring with Alyvix
Overview User Roles Nodes RDP Client Building Tools Editor: Interface Overview Editor: Script Building Editor: Managing Scripts Designer: Interface Overview Designer: Interface Options Designer: Component Tree Selector: Interface Overview Test Case Management Dashboard Use Cases
ntopng Visual Monitoring with Alyvix Elastic Stack IT Operations (Command Orchestrator) Asset Management Service Level Management Cyber Threat Intelligence - SATAYO Introduction to NetEye Monitoring Business Service Monitoring IT Operation Analytics Visualization Network Visibility Log Management & Security Orchestrated Datacenter Shutdown Application Performance Monitoring User Experience Service Management Service Level Management & Reporting Requirements for a Node Cluster Requirements and Best Practices NetEye Satellite Requirements TCP and UDP Ports Requirements Additional Software Installation Introduction Single Node Cluster NetEye Master Master-Satellite Architecture Underlying Operating System Acquiring NetEye ISO Image Installing ISO Image Single Nodes and Satellites Cluster Nodes Configuration of Tenants Satellite Nodes Only Nodes behind a Proxy Additional NetEye Components Single Node Cluster Node Satellites Nodes only Verify if a module is running correctly Accessing the New Module Cluster Satellite Security Identity and Access Management External Identity Providers Configure federated LDAP/AD Emergency Reset of Keycloak Configuration Advanced Configuration Roles Single Page Application in NetEye Module Permissions and Single Sign On Within NetEye Importing User Federation Groups inside another Group Importing OIDC IdP Groups inside another Group Resources Tuning Advanced Topics Basic Concepts & Usage Advanced Topics Monitoring Environment Templates Monitored Objects Import Monitored Objects Data Fields Deployment Icinga 2 Agents Configuration Baskets Dashboard Monitoring Status Icinga2 Features VMD Permissions Notifications Jobs API Configuring Icinga Monitoring Retention Policy NetEye Self Monitoring Concepts Collecting Events Add a Filter Node WHERE Conditions Iterating over Event fields Retrieving Payload of an Event Extract Variables Create a Rule Tornado Actions Test your Configuration Export and Import Configuration Example Under the hood Development Retry Strategy Configuration Thread Pool Configuration API Reference Configure a new Business Process Create your first Business Process Node Importing Processes Operators The ITOA Module Configuring User Permissions Telegraf Metrics in NetEye Telegraf Configuration Telegraf on Monitored Hosts Visualizing Dashboards Customizing Performance Graph The NetEye Geo Map Visualizer Map Viewer Configuring Geo Maps NagVis Audit Log Overview Shutdown Manager user Shutdown Manager GUI Shutdown Commands Advanced Topics Overview User Role Management Cube Use Cases ntopng and NetEye Integration Permissions Retention Advanced Topics Overview User Roles Nodes RDP Client Building Tools Editor: Interface Overview Editor: Script Building Editor: Managing Scripts Designer: Interface Overview Designer: Interface Options Designer: Component Tree Selector: Interface Overview Test Case Management Dashboard Use Cases Overview Architecture Authorization Kibana Elasticsearch Cluster Elasticsearch Configuration Replicas on a Single Node Elasticsearch Performance tuning Overview Enabling El Proxy Sending custom logs to El Proxy Configuration files Commands Elasticsearch Templates and Retentions El Proxy DLQ Blockchain Verification Handling Blockchain Corruptions El Proxy Metrics El Proxy Security El Proxy REST Endpoints Agents Logstash Elastic APM Elastic RUM Elastic XDR Log Manager - Deprecated Overview Authorization in the Command Orchestrator Module Configuring CLI Commands Executing Commands Overview Permissions Installation Single Tenancy Multitenancy Communication through a Satellite Asset collection methods Display asset information in monitoring host page Overview Customers Availability Event Adjustment Outages Resource Advanced Topics Introduction Getting Started SATAYO Items Settings Managed Service Mitre Attack Coverage Changelog Before you start Update Procedure Single Node Upgrade from 4.44 to 4.45 Cluster Upgrade from 4.44 to 4.45 Satellite Upgrade from 4.44 to 4.45 DPO machine Upgrade from 4.44 to 4.45 Create a mirror of the RPM repository Sprint Releases Feature Troubleshooting Tornado Networking Service Management - Incident Response IT Operation Analytics - Telemetry Identity Provider (IdP) Configuration NetEye Cluster on Microsoft Azure Introduction to NEP Getting Started with NEPs Online Resources Obtaining NEP Insights Available Packages Advanced Topics Upgrade to NetEye 4.31 Setup Configure swappiness Restarting Stopped Services Enable stack traces in web UI How to access standard logs Director does not deploy when services assigned to a host have the same name How to enable/disable debug logging Activate Debug Logging for Tornado Modules/Services do not start Sync Rule fails when trying to recreate Icinga object How to disable InfluxDB query logging Managing an Elasticsearch Cluster with a Full Disk Some logs are not indexed in Elasticsearch Elasticsearch is not functioning properly Reporting: Error when opening a report Debugging Logstash file input filter Bugfix Policy Reporting Vulnerabilities Glossary

Designer: Interface Overview

The Alyvix Designer interface consists of two elements:

  • A screen capture image to use for creating and resizing selections and regions of interest around visual elements

  • A panel for indicating how those visual elements should be interpreted and interacted with

Although Designer is intended to be used in conjunction with Alyvix Editor, you can also run it as a standalone component from the command line as follows (you can find information about its command arguments here):

C:\Alyvix\testcases> alyvix_designer

When a screen grab begins, the current screen is captured (it will turn white for a second while the capture process is underway). It then displays the screen capture at full resolution with purple crosshairs that track the mouse, and a semi-transparent reminder PRESS ESC TO OPEN DIALOG is overlaid at the top left as shown here:

The initial Alyvix Designer selection cursor

Tip

Having a second monitor will enable you to mark selections and regions of interest with Alyvix on one screen, while the second screen can still be used for other applications. At the moment, Alyvix can only grab the screen on the main monitor (monitor 0).

Each screen capture is associated with a test case object, which can recognize and interact with up to three groups of visual elements. The color of the crosshairs indicates whether you are working with the first (purple/red), second (green), or third (blue) group.

Pressing Escape will bring up the Designer interface as in the following screenshot, where no groups (or components) have yet been defined. The principle interface elements are (the standalone version of Alyvix Designer is shown here):

The empty Alyvix Designer interface
  1. The Object name (title) of the test case object, which together with the file name is used to uniquely identify this test case object in Alyvix Selector and Editor

  2. Test case object options, which affect all visual elements in the component tree as a whole; when run from Alyvix Editor, the Timeout and Break options will be shown instead in the Selector panel

  3. The component tree subpanel, showing all defined selections and regions of interest that can be interacted with along with their type (image, region or text)

  4. Component options, which depend on the type you assign to the currently selected component in the component tree

  5. Interface controls that allow you to either continue editing on the screen capture, or exit Designer.

When Designer is started without any arguments as above, it assigns the default name VisualObject1 to the test case object, along with the default options Appear, Timeout [sec]: 10, and Break: Yes.

When no visual elements have been selected from the screen capture, the component tree will be empty with only a single root element marked S, along with the thumbnail of the full screen capture.

Selections, Subselections and Regions of Interest

To add a new visual component to the tree, you must be in capture mode. If instead the Designer or Editor interface is visible, press EDIT in the bottom right hand of the panel to return to the screen capture interface containing the crosshairs.

Selections (and subselections) can be made with the mouse in one of two ways:

  • Manually: Hold the left mouse button down to create a selection or subselection (drawing a rectangle around the desired area), and then release when done.

  • Autocontour: Right click on a visual element to use Alyvix’s visual recognizer to automatically determine the relevant selection or subselection. Candidate elements can be discovered by pressing Space, and then pressing it a second time to return to the standard screen capture.

For instance, you can manually select the Windows Start button using the left mouse button as shown in the middle image here:

Before and after creating a selection in the screen capture.

After making a selection, you can then make up to 4 subselections within that group, where their positions will be relative to the main selection. For instance in the example image above, a subselection has been made containing the Windows Cortana search box.

Unlike the main selection, a subselection consists of two overlapping areas rather than a single one. You can resize the two areas independently, although the smaller box, which is the subselection itself, will always remain contained within the larger one, known as the region of interest (or RoI).

The subselection represents what Alyvix should be looking for, while the region of interest represents the space in which it should search for that subselection, relative to the main selection. The region of interest can be expanded to the edges of the screen if necessary, which is useful for example when windows or panels can change size dynamically.

Tip

Making the region of interest wider or taller can be very helpful for GUI elements that “float” relative to the anchoring selection, such as the window controls when a window is resized.

In order for a group to be considered matched, ALL selections and subselections (within their respective regions of interest) must match the screen at the same time. In turn, in order for a test case object to be considered matched, ALL of its groups must match the screen at the same time.

When creating components, the following keyboard shortcuts are available:

Shortcut

Focus is on

Resulting Action

LeftClick(Hold)

<Nothing>

Create a selection or subselection

LeftClick(Hold)

Selection

Move a selection or subselection somewhere else

RightClick

<Nothing>

Autocontour the screen element around the pointer

RightClick

RoI Edges

Push the edge of the RoI under the mouse all the way to the border of the screen.

Ctrl + LeftClick

Subselection

Reset all RoI edges of the subselection to their defaults.

Ctrl + RightClick

Subselection

Remove an entire component (subselection and RoI).

Ctrl + Z

Component

Undo the most recently added component

Ctrl + Y

Component

Re-add the component just removed


Returning from Screen Capture Mode

When in screen capture mode, pressing the Escape key will return you to either the Alyvix Designer or Editor interface. As you make new selections and subselections, they will appear as components within the component tree as shown here:

Adding a first component in the Alyvix Designer interface

Continuing the example from above, the main selection (the Windows Start button) is automatically set as the group element since it was selected first, while the second area (the Cortana search box) is set as the first component (subselection) within that group.

Interface Controls

At the bottom of the Designer panel below the component tree are three actions:

  • OK — Save the current test case and exit. If you did not supply a file name when you started Designer, it will use the value for Object name as the file name.

  • CANCEL — Exit Designer without saving the test case.

  • EDIT — Return to the screen capture interface.