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

[DOCS] Clarify the frequency of config polling #3799

Merged
merged 3 commits into from
Sep 17, 2024

Conversation

lucabelluccini
Copy link
Contributor

What does this PR do?

Clarify the frequency of config polling

private static final int DEFAULT_POLL_DELAY_SEC = (int) TimeUnit.MINUTES.toSeconds(5);

Copy link
Contributor

@JonasKunz JonasKunz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, if @jackshirazi agrees I'll take care of this PR.
The markdown file is actually auto-generated, we'll need to add the paragraph in the Java sources instead.

@jackshirazi
Copy link
Contributor

@JonasKunz yes please

@JonasKunz JonasKunz enabled auto-merge (squash) September 17, 2024 13:00
@JonasKunz JonasKunz merged commit 0ab2a3a into elastic:1.x Sep 17, 2024
14 checks passed
@JonasKunz
Copy link
Contributor

JonasKunz commented Nov 18, 2024

This PR was merged on the wrong branch (1.x instead of main). We'll have to reopen it on the correct branch, otherwise it causes conflicts during release. I had to revert this PR on 1.x to proceed with the release.

JonasKunz added a commit to JonasKunz/apm-agent-java that referenced this pull request Nov 18, 2024
JonasKunz added a commit to JonasKunz/apm-agent-java that referenced this pull request Nov 21, 2024
---------

Co-authored-by: Jonas Kunz <jonas.kunz@elastic.co>
JonasKunz added a commit that referenced this pull request Nov 21, 2024
---------

Co-authored-by: Luca Belluccini <luca.belluccini@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants