Thread
#secoda-feature-requests
    a

    adventurous-furniture-1306

    11 months ago
    Feature Request: process the Looker query slug. The usage/popularity query running against Snowflake will likely primarily return our Looker service user, which is only so useful. The query slug is included in the query_text, and looks like this:
    -- Looker Query Context '{"user_id":194,"history_id":7718638,"instance_slug":"ee4910e2194d0857f445e289e32c201f"}'
    If you’re connecting to the Looker API, you can snag the user ID, email, and name from Looker, and match it up to the parsed user_id from the query slug.
    e

    elegant-house-93198

    11 months ago
    We’ve had a number of customers flag this issue, so we’ll be adding the ability for a user to specify which accounts to ignore when it comes to the number of queries. Since many people have asked for this, it’s high up in the list of improvements
    a

    adventurous-furniture-1306

    11 months ago
    Knowing the users coming in from Looker is useful to us. I have very few actual Snowflake users, so most usage is coming from service users, which do have actual people on the other side.
    e

    elegant-house-93198

    11 months ago
    That’s good context. We want to make it so that marking who is real vs. not is a manual process so that we don’t mess that up. We’ll just be displaying all the users that we see in Snowflake/Looker