Limit Consul Connect targets to local instance of a Nomad system job

We have a Nomad system job for our log aggregator running on all nodes in the cluster and were hoping to find a way for our Nomad applications to reach this local aggregator via Consul Connect.

We sort of made it work by creating a prepared query in Consul and adding "Near": "_agent", to it, but this seems to just put the local aggregator as the first instance in the list, but all other instances of the aggregator on other nodes are included as well.

Is there a way to limit the prepared query to only return the local instance of the aggregator? Or, is there any other way to limit this so Consul Connect will only proxy to the local instance of the aggregator?