8000 Add context of query so that Usage Analytics is more refined · Issue #7033 · lightdash/lightdash · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Add context of query so that Usage Analytics is more refined #7033
Open
@joaoviana

Description

@joaoviana

Description

Currently we display the users that made the most queries in the last 7 days on Usage Analytics feature.
For example:
image

It would be useful to know in what context these users were in when that query count increased.

What has been reported is that this count also increases for Scheduled Deliveries. Since that's an automated process, should it be part of this count metric? I believe not.

Code

add context(or similar... action?) to:
type DbUserWithCount = {
user_uuid: string;
first_name: string;
last_name: string;
count: number | null;
};

So that we can count queries that users performed on charts, dashboards, scheduled deliveries, syncs, exports, etc

Acceptance criteria

  • users who have run the most queries in the last 7 days has the total queries broken out across the different query_source options (as well as the total queries)

Docs

to:

  • Users that have run the most queries in the last 7 days: a list of the users that have run the most queries in your project in the last 7 days. This shows the total queries, and also the queries broken out across different query sources.

  • Add a note above Here's an overview of the fields used in the dashboard: saying:

:::info
Unless specified, the count of queries includes queries executed from running scheduled deliveries, syncs, exports, viewing charts or dashboards, and running queries in the Explore view.
:::

Metadata

Metadata

Assignees

No one assigned

    Labels

    staleIssue hasn't been updated for 60 days✨ feature-requestRequest for a new feature or functionality📖 documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0