All connections and scans of external systems to IBM software should be visible, manageable and auditable to business users through the User Interface

Consistent with scans (metadata discovery, get lineage, enrichment), any query or scan run against an external source system such as Teradata should be visible through the user interface so business users can properly view, manage and audit these types of queries.

When running scans (e.g. metadata import – discovery, get lineage & enrichment) on an external source – there is clear visibility and control of those scans, including the ability to limit the access to who can run the scans, and ability for admin users to see scans are running, pause and stop the scans, as well as view the logs. However, there are a number of user screens within Cloud Pak for Data that can trigger a scan of the source system to update information on the page the user is viewing (Project - preview asset and profiling tabs, Catalogue - asset and profiling tabs). When this occurs, there is no visible way for any user to see, monitor or influence (pause/stop) the scan running against the source system or view the logs for these scans through the user interface. The cache for data on these pages only lasts for 1 hour. With a large number of users accessing a large number of pages, this could result in a large number of headless queries, which creates a risk of having a negative impact on the source system that already has a large number of users. Also, it is also not always obvious to users exploring a data asset that they have triggered a scan against the source data.