Introduction

Oplon Analytics is Oplon’s advanced solution for analyzing web traffic data. Precisely integrated with Oplon Secure Access, the system enables the collection, processing, and interpretation of data generated from web traffic in real time.

The platform offers advanced reporting capabilities, using dynamic charts and sophisticated analytical tools to provide detailed insights, Oplon Analytics transforms raw data into strategic information.

With Oplon Analytics, optimizing marketing campaigns, identifying trends and defining winning strategies become facilitated processes. This technology solution places complete control over web traffic dynamics in the hands of users, enabling efficient and informed management of business resources.

Architecture

The suggested minimum architecture is to have one node (usually an Oplon Secure Access node) producing data, and the Oplon Analytics node consuming and logging. Other types of architecture are possible, even the simplest single Oplon Secure Access + Analytics node, but they will not be covered in this guide.

This guide will focus on installing and configuring the Oplon Analytics node and configuring the Oplon Secure Access node to send statistics to the Oplon Analytics node.

The Virtual Appliance that is delivered generally already has some steps in this guide, generally contains a PostgreSQL type DB, and will have Matomo used internally as the analytics collector.

Virtual Appliance import and first boot of Oplon Analytics

The import and first boot follows evenly the guide on installing Oplon Secure Access until the first access to the dashboard shown here: https://archive.oplon.net/en/docs/osa-setup 

For clarity, the points are:

• Import
• Assigning a static ip
• First configuration Management Console and Password Delegate

License installation

For proper installation, the two licenses must be installed:

• Catalog: in the Oplon Secure Access nodes;
• Traffic Monetizer: in the Oplon Analytics node within the A05_LBLGoStatisticWebCache module.

After that, restart the service using the oplonrestart command.

Configure WebCache

A05_LBLGoStatisticWebCache is the service responsible for receiving statistics from consumer nodes and writing them to the database. This service should only be active in the Oplon Analytics node. Now it is necessary to configure:

• the Oplon Analytics node: go to Modules->Statistic brokers->Edit and change (from the node variables) the variable LBL_GLOBAL_ADDRESS_BROKERWEBCACHE with the IP address of the Oplon Analytics node (the port is 5994), then run “Save and Reinit”. Go to the Webcache basic parameters panel in Modules->Statistic brokers->Edit, enter the data for the PostgreSQL DB connection (if you have installed the VAPP that Oplon delivered to you, the DB connection has already been set up) and restart the A05_LBLGoStatisticWebCache module via: Stop Module + Start Module;
• the Oplon Secure Access nodes: in the producers you can edit any module to access the node variables, so for simplicity go to Modules->Statistic brokers->Edit and edit (from the node variables) the variable LBL_GLOBAL_ADDRESS_BROKERWEBCACHE with the IP address of the Oplon Analytics node (port is 5994), then run “Save and Reinit”. This will instruct the producers to send the statistics to the Oplon Analytics node.

Check & Troubleshooting

Check writing to DB

To verify that the node correctly receives data and writes it to the DB, you need to make sure that:

• video logging or ssh logging has been enabled on the RAG  configuration of the Oplon Secure Access nodes;
• traffic has been made by connecting in ssh or rdp;
• the Oplon Secure Access node to which you have connected to make ssh or rdp traffic has as its node variable LBL_GLOBAL_ADDRESS_BROKERWEBCACHE valued with the ip address of the Oplon Analytics node;
• the Oplon Analytics node connects correctly to the DB and then verify the data entered the Webcache basic parameters panel in Modules->Statistic brokers->Edit
• connect to the DB and run a query on the SSHARE_ACCESSES table to verify accesses, on the SSHARE_RD table to verify RDP connections, on the SSHARE table to verify SSH connections.