In T347430: [Data Platform] Install a Prometheus connector for Presto, pointed at thanos-query a Prometheus connector for Presto was created that makes it possible in Superset's SQL Lab facilities to then join data between Prometheus and other data lake tables from its web UI.

@nettrom_WMF noted on Slack encountering an error when attempting to query a particular table.

... mediawiki_wikimediaevents_edits_total. The table shows up in the list if I search for it in "see table schema", but triggers some errors ("An error occurred while fetching table metadata"), and if I try to run a query against it it errors out with The table "thanos.default.mediawiki_wikimediaevents_edits_total" does not exist.

Your task filer also encountered this elsewhere. Some Test Kitchen (FKA Experimentation Lab) work might be a little simpler on the Superset dashboard side absent this behavior.

It appears that if a Thanos / Prometheus metric name has uppercase characters, although the corresponding table shows as existing in Superset (as with a Presto command line shell), if attempting queries against that table (as with a Presto command line shell), the data is inaccessible. It seems that for metric names that do not involve an uppercase character, this is probably not an issue, at least not that your task filer has encountered.

Screenshots included below.

In other systems, sometimes a re-import of table metadata, possibly with adherence to case sensitivity for the imported table names, is required to resolve this sort of situation. What appears to be happening is that the metric name table alias is being presented as a lowercase mapping, when in fact the metric name in Thanos is mixed-case. It's not clear if a metadata reimport might resolve this here, or if there's something a little subtler that may need a code change upstream, though.