Hub Reporting

The Hub prepares and provides content for multiple peripheral SUSE Manager Servers. The goal of the reporting feature is to get data from these Servers back and have combined reporting data available on the Hub. The data is made available for external Reporting Tools.

1. Architecture

The main database is a PostgreSQL database in the SUSE Manager Hub system. It stores all the information collected from all the servers, and aggregates them. Every peripheral Server has its own reporting database where the information is collected for that system. In summary:

  • the DB in SUSE Manager Hub stores, collects and aggregates data coming from all the DBs of the peripheral Servers,

  • the DB in SUSE Manager Hub stores also its own data from the systems directly connected and managed by the Hub,

  • the DB in peripheral SUSE Manager Server stores its own data,

  • the reporting tool can be connected either to the Hub or to any SUSE Manager Server.

2. Setup

The reporting database and schema are set up by default using the local PostgreSQL server. The reporting database is a separate database accessible via the network.

As a requirement we expect all server certificates are signed by the same Root Certificate Authority (CA). The whole SUSE Manager Hub environment should be using only one Root CA.

2.1. Create a DB user for the reporting

Before connecting an external Reporting Tools to the Database, a user with read-only permission should be created. For doing that, it is possible to use uyuni-setup-reportdb-user.

usage: uyuni-setup-reportdb-user [options]

            show this help message and exit
            Switches to non-interactive mode
            Report DB User
            Report DB Password
            Add the new user
            Delete the user
            Set a new password

3. Database Schema

The schema exports the most important tables from the main SUSE Manager Database as a de-normalized variant containing only data which are relevant for a report.

Ready-to-use reports are provided as views, aggregating data over multiple tables.

Every table gets an extra id column (mgm_id) specifying the SUSE Manager server which provided the data. On a single SUSE Manager Server this column has the standard value 1 which represent localhost. On the SUSE Manager Hub it is replaced with the real server id the managed server has in the hub database.

Another common additional field is synced_date, which represents the time when the data were exported from the main SUSE Manager Server database.

Navigate to Help  Report Database Schema to find the schema documentation.

4. Data Generation and Update

SUSE Manager uses taskomatic jobs to generate the data for the reporting database and to get the data from the peripheral servers to the hub.

To generate and update the data on a peripheral server, the responsible schedule is called update-reporting-default. It is executed by default daily at midnight.

On the SUSE Manager Hub there is a second schedule which is important. To fetch the reporting data from all registered peripheral servers, the task with the name update-reporting-hub-default is executed daily at 1:30 AM.

All times are in the local timezone of the server. If the peripheral servers are in different timezones, it is recommended to align all the schedules. Make sure that all reporting data are gathered at a specific point in time, and update-reporting-hub-default is running when all peripheral servers have actually finished their local jobs.

4.2. report_db_batch_size


The maximum number of rows fetched and written from one database to the other in one shot.

Tune when

Out of memory errors or on processing speed problems.

Value default


Value recommendation

500 - 5000




report_db_batch_size = 4000

After changing

Check memory usage. Monitor memory usage closely before and after the change.

4.3. report_db_hub_workers


The maximum number of workers requesting data from peripheral servers on a hub at the same point in time.

Tune when

The number of peripheral servers increases significantly (more than 100), or a faster synchronization is required.

Value default


Value recommendation

2 - 10




report_db_hub_workers = 5

After changing

Check memory usage. Monitor memory and cpu usage of the hub closely before and after the change. Also monitor the load, cpu and memory usage of the reporting database of the hub.


All the data collected from the peripheral server must be written into the hub reporting database. Tuning that database could increase the performance as well.