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

Query Metrics Missing Filters - grpc: received message larger than max (6870037 vs. 4194304) #2613

Open
1 task done
wobo-mattmencel opened this issue Nov 9, 2023 · 1 comment
Assignees
Labels
bug Bug report

Comments

@wobo-mattmencel
Copy link

Description

PMM is running in Kubernetes. When I go to the Query Metrics page, using the default 12h timeframe, the Filters pane has a spinning wheel for a few seconds. Then I see the grpc error...
grpc: received message larger than max (6870037 vs. 4194304)

... and the Filters pane is empty.

If I cut the timeframe shorter, e.g. 1 hour, it works.

Tested without resource requests/limits set, and then set both to 8Gi. Same result either way.

If you'd like a HAR file from my browser just let me know where I can send it.

Expected Results

I should be able to filter query metrics on the 12 hour timeframe, or longer.

Actual Results

I cannot filter query metrics on the 12 hour timeframe.

Version

2.40.1

Steps to reproduce

No response

Relevant logs

No response

Code of Conduct

  • I agree to follow Percona Community Code of Conduct
@nickhelmet
Copy link

I'm running PMM version 2.42.0 in Kubernetes and encountering the same issue when trying to retrieve data for the last 12 hours (which is the default value).
Already tried increasing memory and CPU resources

grpc: received message larger than max (9072301 vs. 4194304)

@artemgavrilov artemgavrilov removed their assignment Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug report
Projects
None yet
Development

No branches or pull requests

4 participants