Hub Reporting

Hub Reporting extends the Reporting Database feature by aggregating reporting data from all connected peripheral SUSE Multi-Linux Manager servers into a single central reporting database on the Hub.

For general reporting database setup, user creation, schema documentation, and Grafana dashboard integration, see Reporting Database.

1. Hub Architecture

In a hub deployment:

  • the reporting database in the SUSE Multi-Linux Manager Hub stores, collects, and aggregates data coming from the reporting databases of all peripheral servers,

  • the reporting database in the SUSE Multi-Linux Manager Hub also stores its own data from systems directly connected to and managed by the Hub,

  • the reporting database on each peripheral SUSE Multi-Linux Manager server stores only its own data,

  • external reporting tools can connect to either the Hub or any peripheral SUSE Multi-Linux Manager server.

The connection between hub and peripheral servers is established via hub online synchronization. For more information, see Hub Online Synchronization.

2. Hub Data Aggregation

The update-reporting-hub-default schedule fetches and aggregates reporting data from all registered peripheral servers. For a description of both taskomatic reporting schedules, see Reporting Database.

If peripheral servers are in different timezones, align all update-reporting-default schedules so that every peripheral server has finished its local job before update-reporting-hub-default runs on the Hub.

3. Tuning

3.1. report_db_hub_workers

Description

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

2

Value recommendation

2 - 10

Location

/etc/rhn/rhn.conf

Example

report_db_hub_workers = 5

After changing

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.

Notes

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.

For the report_db_batch_size tuning parameter, which applies to all servers including the hub, see administration:reporting-database.adoc#reportdb-batch-size.