Background:
We have telegraf running on the host machine as the sink for metrics for all the services (nomad, consul, vault as well as containers ran by nomad).
The problem is that when we setup the service mesh, we want to have enovy proxy also emit its metric to the telegraf agent on the host network.
What we are able to get it working is to hardcode the host ip address in the envoy_dogstatsd_url
:
connect {
sidecar_service {
proxy {
config {
envoy_dogstatsd_url = "udp://172.16.71.143:8125"
}
}
But what we really want to have is a dynamic ip in there, like:
connect {
sidecar_service {
proxy {
config {
envoy_dogstatsd_url = "udp://${attr.unique.network.ip-address}:8125"
}
}
to be able to render the host ip into the job file dynamically. But this is not something we can do today.
Would this be a valid request to add variable templating into that field?