Skip to content

Handle the possibility that the agent hasn't started yet #5669

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

Open
BridgeAR opened this issue May 6, 2025 · 1 comment
Open

Handle the possibility that the agent hasn't started yet #5669

BridgeAR opened this issue May 6, 2025 · 1 comment

Comments

@BridgeAR
Copy link
Collaborator

BridgeAR commented May 6, 2025

Discussed in https://github.com/DataDog/dd-trace-js/discussions/5257

Originally posted by adamdavis40208 February 12, 2025
We're noticing that sometimes a new k8s node will get created, a node service placed on the cluster, and that pod spazzing out because the agent isn't available.

DATADOG TRACER DIAGNOSTIC - Agent Error: socket hang up
Received SIGTERM. Shutting down
SIGINT Received, stopping consumer

Sure, we just spin up another pod and try again, but it'd be nice if this could be retried a few times

@BridgeAR
Copy link
Collaborator Author

BridgeAR commented May 6, 2025

I think we should support a retry mechanism to gracefully handle cases like that for a startup time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant