fix: heartbeat timeout for integrations #2160
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abhishuraina
force-pushed
the
NR-492260-infra-agent-timeout-option-for-integrations-not-honored-by-the-infra-agent
branch
from
c672b1b to
cc5e708
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The heartbeat timeout issue has been fixed. From the new version, we'll use a variable
heartbeat_timeoutattribute to accept the heartbeat timeout value for integrations.The reason for not using TIMEOUT is that it is used by SQL integrations to wait a defined number of seconds for a database connection.
Sample config
integrations:
env:
HOSTNAME: localhost
PORT: 5432
DATABASE: postgres
COLLECTION_LIST: 'ALL'
TIMEOUT: 300s
heartbeat_timeout: 140s
interval: 60s