Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metrics Api defaults to LIMIT 500 #2730

Open
dngferreira opened this issue May 7, 2024 · 1 comment
Open

Metrics Api defaults to LIMIT 500 #2730

dngferreira opened this issue May 7, 2024 · 1 comment

Comments

@dngferreira
Copy link
Contributor

dngferreira commented May 7, 2024

Describe the Bug

Even when the number of views is higher than that it only returns 500 rows.
This makes the data that are shown on the /[websiteId}/?view=query incorrect and show different results (counts) when you apply a search.
Maybe it the LIMIT should be set to the number of views on the page.

Database

PostgreSQL

Relevant log output

No response

Which Umami version are you using? (if relevant)

v2.11.1

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

Docker

@franciscao633
Copy link
Collaborator

I don't think its the limit 500 that's causing the issues. the limit is applied after aggregating the data so its just limiting the result set to the top 500 groupings.

image

The query parameters would be the only metrics where applying a search changes the counts since in our db multiple query params are under a single column.

ref=umami-hero&utm_source=google-ads&utm_medium=paid-search&utm_campaign=GAds-Website-Analytics&utm_agid=158289285006&utm_term=website+analytics&creative=692822853771&device=m&placement=&gad_source=1&gclid=CjwKCAjwl4yyBhAgEiwADSEjeFshoDs43LnhlD3QhujLGFGUwYfMEP8z8hBXSd-5RHLGsHyrYQTFqhoCXiAQAvD_BwE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants