Haïssam Kaj
Haïssam Kaj
Hi @jorgenbs Thank you for the detailed report. Have you tried using the agent's service discovery? It's made specifically for this kind of setup. You will find documentation about it...
Ah nevermind, I replied too quickly. Reaching processes from another container (even in the same pod) is not yet possible in Kubenetes (it's actually a docker limitation). So besides shipping...
Hi @therc Sorry for the delay, looks like we lost track of this one. - for etcd monitoring we recommend deploying the agent on etcd nodes and running the etcd...
Hi @mausch, thanks for taking the time to report this. You're right, setting up bind before connect would require using a lower-level tool than `requests`. A solution if you're expected...
yeah that makes sense. Adding it to the backlog.
Hey @therc, @c-knowles Thanks for the feedback. We are in the process of addressing the issue of cluster-level metrics/metadata/events, so stay tuned about this. Meanwhile, the current recommended way is...
@c-knowles Running two agents on the same node can lead to wrong values for some metrics because it's not always clear in the backend what to do with two points...
Hi @dennari Thanks for notifying us of this. To help us investigate, could you please send us a flare from this agent when it's pegging cpu? Instructions can be found...
@dennari the command is interactive. Try with `docker exec -it 4d61f6506e73 /opt/datadog-agent/bin/agent flare` ?
thanks @dennari I'll have a look asap