How to properly clean redundant and uneeded host facts data stored in Satellite 6?

Solution Verified - Updated -

Issue

Host Facts are stored during host registration and ongoing periodic uploads during normal operation. If there are too many facts stored in Satellite, it might affect the performance of the Satellite server. Most users of Satellite don't use all the facts reported and stored in the database. There are often cases when there are are tens of thousands of facts per host which can lead to very large tablesizes in the Satellite 6 database.

Recently, with the increase in adoption of OpenShift and containers, the number of facts reported by hosts are going up rapidly in customer environments. For example, this can happen if many network interfaces are created and deleted. We already filter out some facts (by default) which caused issues in the past, but there are some new fact offenders that were found recently while working with some of our large customers.

  • Satellite performance is poor
  • you find a large number of long running queries in PostgreSQL associated with fact_names or fact_values.
    • Note: Enable log_min_duration_statement in PostgreSQL configuration to log long running queries.
  • our systems were reporting to Satellite6 redundantly detailed facts that slowed down facts processing
  • setting "Ignore interfaces with matching identifier" and/or "Exclude pattern for facts stored in satellite" was updated accordingly to prevent storing new redundant facts
  • how to prune out stored facts?

Environment

Red Hat Satellite 6.4+

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In