Minimum delay for retries when central config cannot be retrieved

[jaggederest]

In the Ruby Agent we had a report of unbounded memory growth when the central configuration server (APM Server) is offline and behind a reverse proxy which does not return empty payloads.

This behavior would be avoided if there were a minimum retry time and rate, per the spec change.

As these changes are optional and suggested, I opted for the shorter template without a meta issue.

• May the instrumentation collect sensitive information, such as secrets or PII (ex. in headers)?
  • [ ] Yes
  • [ ] Add a section to the spec how agents should apply sanitization (such as sanitize_field_names)
  • [x] No
  • [ ] Why?
  • [ ] n/a
• [x] Create PR as draft
• [x] Approval by at least one other agent
• [x] Mark as Ready for Review (automatically requests reviews from all agents and PM via CODEOWNERS)
  • Remove PM from reviewers if impact on product is negligible
  • Remove agents from reviewers if the change is not relevant for them
• [x] Approved by at least 2 agents + PM (if relevant)
• [ ] Merge after 7 days passed without objections \ To auto-merge the PR, add /schedule YYYY-MM-DD to the PR description.
• [ ] Create implementation issues through the meta issue template (this will automate issue creation for individual agents)

/schedule 2022-09-21

[apmmachine]

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

#### Build stats * Start Time: 2022-09-19T04:24:00.116+0000 * Duration: 3 min 12 sec

[jaggederest]

Also, I seem to remember us discussing whether this needs to use the full PR process - if that's the case should I reopen a new PR for this branch using the template?

[felixbarny]

No, just replace the PR description with the checkboxes of the full process.