Thank you Charles, I did try this and in my particular case it didn't work.
I had it listening on .176 but netstat showed .175 as the address being
used to create tcp connection.

On Sat, Jan 23, 2021, 12:51 AM Charls P John <[email protected]> wrote:

> I am not sure whether it work, but did you try prometheus on node1 to
> listen only on your desired ip?
>
> On Sat, Jan 23, 2021, 00:58 Vishal <[email protected]> wrote:
>
>> Sorry for the typos earlier...
>>
>> On Friday, January 22, 2021 at 1:25:05 PM UTC-6 Vishal wrote:
>>
>>> Hello,
>>>
>>> In our setup, a Prometheus on node 1 scrapes from Prometheus on nodes 2
>>> and 3.
>>> Node 1 has 2 IP addresses (.175 and .176) on eth1.
>>>
>>> Is it possible for us to select the source IP address anywhere in
>>> Prometheus configuration when sending scrape requests to node 2 and node 3?
>>>
>>> Sincerely,
>>> Vishal
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Prometheus Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/prometheus-users/82c942ec-18f7-41d2-b370-22f47c7787c1n%40googlegroups.com
>> <https://groups.google.com/d/msgid/prometheus-users/82c942ec-18f7-41d2-b370-22f47c7787c1n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/CAFA%2BBR7f-W%2B6ijQvsdSi%3DzHH2XGT3mAq4O%2B8%2BebxdCh8t9MsBA%40mail.gmail.com.

Reply via email to