Conversation
|
This pull request does not have a backport label. Could you fix it @pchila? 🙏
NOTE: |
|
|
|
This pull request is now in conflicts. Could you fix it? 🙏 |
6275ce9 to
4885a96
Compare
5e6bc04 to
38bd965
Compare
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
blakerouse
left a comment
There was a problem hiding this comment.
More testing code then actual change code. I appreciate the attention to coverage in this change, well done!
andrzej-stencel
left a comment
There was a problem hiding this comment.
I'm not seeing any validation for the value of SamplingRate. Should there be any? I assume the value of SamplingRate should be a positive number lower than 1?
According to the APM documentation https://www.elastic.co/guide/en/apm/agent/go/current/configuration.html#config-transaction-sample-rate it should be a float between 0.0 and 1.0 If we have to add a validation also on agent side we would need to rely on |
ac25571 to
3bde46d
Compare
|
|
SonarQube is complaining about lines in |
* Update elastic-agent-client dependency to 7.16.0 * Add support for APM sampling rate config * fixup! Add support for APM sampling rate config * Add unit tests for APM config triggering component changes * make notice (cherry picked from commit b284e56) # Conflicts: # go.mod # go.sum
* Update elastic-agent-client dependency to 7.16.0 * Add support for APM sampling rate config * fixup! Add support for APM sampling rate config * Add unit tests for APM config triggering component changes * make notice (cherry picked from commit b284e56) # Conflicts: # go.mod # go.sum
* Update elastic-agent-client dependency to 7.16.0 * Add support for APM sampling rate config * fixup! Add support for APM sampling rate config * Add unit tests for APM config triggering component changes * make notice


What does this PR do?
This PR adds the possibility to specify apm sample rate in elastic agent APM configuration
Why is it important?
Specifying a sample rate allows controlling the ingestion rate, reducing overhead and storage requirements when self-monitoring is active
Checklist
[ ] I have made corresponding changes to the documentation./changelog/fragmentsusing the changelog toolDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself