General
Escalation
General
Escalation
Description
How to test
None
How to document
None
AFFECTED CS IDs
CS0040437
Activity
Show:
Nurlan Moldomurov October 22, 2024 at 6:06 AM
Nurlan Moldomurov July 24, 2024 at 9:09 AM
we are planning to close this task as done, could you provide your feedback, please?
Nurlan Moldomurov January 29, 2024 at 11:22 PM
Nurlan Moldomurov January 10, 2024 at 9:51 AM
ability to provide env variable to PMM Server on AMI will be provided in PMM 3
Nurlan Moldomurov November 17, 2023 at 6:07 AM
, could you provide exact command used to run PMM Server docker image? And how did you verify that it doesn't increased the scrape size?
Done
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Reporter
Priority
Medium
Components
Labels
Needs QA
Yes
Needs Doc
Yes
Affects versions
Lead time
196
Smart Checklist
Open Smart Checklist
Open Smart Checklist
Created October 31, 2023 at 7:20 AM
Updated October 22, 2024 at 6:06 AM
Resolved July 31, 2024 at 9:20 AM
Adding PMM_PROMSCRAPE_MAX_SCRAPE_SIZE in /usr/lib/systemd/system/pmm-agent.service to customize scrape size is not respected by vmagent binary:
Then apply configuration and restart pmm-agent:
You can see that pmm-agent uses the environment variable but vmagent does not:
As you can see above that the promscrape.maxScrapeSize is still 64MB and not 12MB.
I suspect it's because of this code:
https://github.com/percona/pmm/blob/main/managed/services/agents/vmagent.go
It looks like the new environment variable will only incorporate existing environment variables prefixed with "VMAGENT_" so "PMM_PROMSCRAPE_MAX_SCRAPE_SIZE" will be excluded.