With the release of https://issues.redhat.com/browse/CHAINSAW-487 , there is a change means that any RHSM registered system (consumer) that does not check in for 30 days will be automatically removed from the RHSM database. However, this behavior seems to differ from the system staleness and deletion settings on console.redhat.com.

There are common scenarios where a system may be offline for weeks or even months but still in use. For example, in lab, cloud, or backup environments. If the RHSM consumer profile is removed at 30 days, even if console deletion is set to a much longer duration, it raises a concern. 

Show a warning banner on console.redhat.com about this new implementation and Staleness notification to customers in advance of a consumer profile being permanently deleted so that the customers can plan a course of action to fix in their env if they don't want the profiles to be automatic deleted. Customer should be able to see the list of consumer profiles scheduled for deletion.  In the HBI, show additional information about the RHSM staleness on top of the HBI staleness.

To avoid panic and confusion, There should be some sort of Email notification as well for the customer prior to the deletion so that they will get notified about the scheduled deletion of their registered system. Otherwise customer will ask who deleted the system and when. Log this event clearly, so admins are aware of why a system disappeared from their inventory.