View the original community article here
Last tested: Nov 19, 2020
To check the performance time of a look in a dashboard, we have to use count on 'queryid' -- there is no direct relationship between lookid and dashboard id.
We rely on queryid is because queryid tells us about a specific query that is sent to database (i.e.: we can change a query underlying in a look or in a dashboard, the queryid will change, while the lookid and dashboard id remain the same -- same address for the house but different people living there is the analogy to this case).
The step would be:
1/ Find the query id of your look
2/ Run the explore with query id and dashboard
3/ Select average time running, source, and other fields if needed
Example:
https://instance.looker.com/explore/system__activity/history?fields=history.min_runtime,history.max_runtime,query.id,history.real_dash_id,dashboard.link,dashboard.id,dashboard.title,history.issuer_source,history.result_source&f[look.id]=&f[dashboard.id]=&f[dashboard.title]=&f[query.id]=59244&sorts=history.min_runtime+desc&limit=500&query_timezone=UTC&vis=%7B%7D&filter_config=%7B%22look.id%22%3A%5B%7B%22type%22%3A%22%3D%22%2C%22values%22%3A%5B%7B%22constant%22%3A%22%22%7D%2C%7B%7D%5D%2C%22id%22%3A0%2C%22error%22%3Afalse%7D%5D%2C%22dashboard.id%22%3A%5B%7B%22type%22%3A%22%3D%22%2C%22values%22%3A%5B%7B%22constant%22%3A%22%22%7D%2C%7B%7D%5D%2C%22id%22%3A1%7D%5D%2C%22dashboard.title%22%3A%5B%7B%22type%22%3A%22%3D%22%2C%22values%22%3A%5B%7B%22constant%22%3A%22%22%7D%2C%7B%7D%5D%2C%22id%22%3A2%2C%22error%22%3Afalse%7D%5D%2C%22query.id%22%3A%5B%7B%22type%22%3A%22%3D%22%2C%22values%22%3A%5B%7B%22constant%22%3A%2259244%22%7D%2C%7B%7D%5D%2C%22id%22%3A3%7D%5D%7D&origin=share-expanded
This content is subject to limited support.