View queries that Sisense is sending to a live source?

You can try the combined.log or the query.log (in var/log/sisense/sisense on your main app node) from, that should have most log records in it.

An actually *failed* query due to an error should have its sql somewhere in query.log.

I think the busy animation on the filters tends to happen when the data security/available rows in the filter queries are running. If you have a lot of data security settings or a lot of rows in your dimension tables, those might be things to check.