Add identifier to automatic metadata introspection queries for traceability

What is the problem or goal the end user is trying to solve or accomplish?

The customer wants to reliably identify the source of automatic metadata introspection queries (SELECT * FROM <table> LIMIT X) that are executed by Preset/Superset. These queries currently lack clear attribution metadata, making it difficult to distinguish them from actual user-initiated queries.

This lack of context complicates internal processes like dataset usage auditing and table deprecation planning, as the team has to manually check each query to determine its origin.

How are they solving it currently?

Manually reviewing query patterns and cross-referencing logs to determine if a query was likely generated by metadata introspection, based on structure and frequency. This is tedious and error-prone, especially at scale.

What is the recommended solution by the Customer?

Include a distinguishing comment in the query (e.g., at the end of SELECT * FROM <table> LIMIT X) when it originates from Superset’s automatic introspection (e.g., -- preset:metadata-introspection). This would allow teams to reliably identify and filter these queries during analysis or auditing.