Thanks Brian for your response. I am good to go now. One last query before 
I go ahead and implement the exporter. Since this is a MySQL cluster, do 
all the three nodes report the same metrics ? Or do the metrics differ for 
each node ? 

Thanks
Y.G

On Saturday, September 9, 2023 at 4:29:57 PM UTC+5:30 Brian Candler wrote:

> You said *"I  want to keep the mysql exporter only on node A and remove 
> it on nodes B and C"*
>
> Then what happens if node A goes down? You'll lose all monitoring of B and 
> C!
>
> If instead you put the exporter on your prometheus server, so that it 
> remotely contacts A, B and C, that might be better. But unless your 
> connections across the network are properly secured (e.g. with TLS and 
> server certificate validation) you may be opening up your mysql server to 
> attack.
>
> Putting the exporters directly on each node eliminates that problem. At 
> worst, an attacker can get access to your metrics - but at least the 
> database access credentials are not being sent across the wire.
>
> On Saturday, 9 September 2023 at 11:29:17 UTC+1 Y.G Kumar wrote:
>
>> Hi,
>>
>> I am trying to find out why the multi target approach is not advisable in 
>> the case of mysql cluster ?
>>
>>
>> On Friday, September 8, 2023 at 5:06:44 PM UTC+5:30 Brian Candler wrote:
>>
>>> Ben's answer was clear and unambiguous, IMO.
>>>
>>> In the case of specific questions about the galera cluster, you'd be 
>>> best to ask your vendor (or test the exporter's behaviour yourself).
>>>
>>> On Friday, 8 September 2023 at 11:07:36 UTC+1 Y.G Kumar wrote:
>>>
>>>> Any update ?
>>>>
>>>> On Thursday, September 7, 2023 at 9:07:34 PM UTC+5:30 Y.G Kumar wrote:
>>>>
>>>>> Ok, to clear the confusion at this point for me, is it good to have 
>>>>> multi target approach in general ?  
>>>>> Also the next question is, in the case of galera cluster, are the 
>>>>> metrics same from each of the exporters ? since galera syncs the data 
>>>>> among 
>>>>> the cluster members ?  Please explain....
>>>>> Appreciate your time Brian and Ben.
>>>>>
>>>>> On Tuesday, September 5, 2023 at 6:37:31 PM UTC+5:30 Ben Kochie wrote:
>>>>>
>>>>>> The exporter is meant to run as a "side car", installed on every node 
>>>>>> of your cluster.
>>>>>>
>>>>>> What you are doing is not following best practices.
>>>>>>
>>>>>> On Tue, Sep 5, 2023 at 2:42 PM Y.G Kumar <ygku...@gmail.com> wrote:
>>>>>>
>>>>>>> Brian,
>>>>>>>
>>>>>>> This is what I am trying to achieve. I have a three node galera 
>>>>>>> mysql cluster on three nodes A, B and C with respective IPs.
>>>>>>> As of now, I have installed mysql exporter in all the above three 
>>>>>>> nodes and trying to access it using haproxy external IP using the above 
>>>>>>> three nodes as backends.  It is working fine. 
>>>>>>>
>>>>>>> Now , I  want to keep the mysql exporter only on node A and remove 
>>>>>>> it on nodes B and C and start the  multi target approach from node A 
>>>>>>> only. 
>>>>>>> So in the /etc/.mysqld_exporter.cnf   file , how do I mention each 
>>>>>>> section 
>>>>>>> of the other two nodes ?  This is my present file content in each of 
>>>>>>> the 
>>>>>>> nodes above:
>>>>>>> ----
>>>>>>> [client]
>>>>>>> user=mysqld_exporter
>>>>>>> password=StrongPassword
>>>>>>> ---
>>>>>>>
>>>>>>> Please suggest..
>>>>>>>
>>>>>>> Appreciate your time.
>>>>>>>
>>>>>>> Good day
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, August 29, 2023 at 12:46:50 PM UTC+5:30 Brian Candler 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> On Tuesday, 29 August 2023 at 07:34:58 UTC+1 Y.G Kumar wrote:
>>>>>>>>
>>>>>>>> Please help ...
>>>>>>>>
>>>>>>>>
>>>>>>>> Please start by reading the documentation at the link I posted 
>>>>>>>> earlier in this thread:
>>>>>>>> https://github.com/prometheus/mysqld_exporter/#multi-target-support
>>>>>>>>
>>>>>>>> Then if you are unable to make this work, you can post a specific 
>>>>>>>> question 
>>>>>>>> <http://www.catb.org/~esr/faqs/smart-questions.html#beprecise>: 
>>>>>>>> show exactly what you configured, what you expected to happen, and 
>>>>>>>> what 
>>>>>>>> actually happened (with any logs or error messages).
>>>>>>>>
>>>>>>> -- 
>>>>>>> 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 prometheus-use...@googlegroups.com.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/prometheus-users/97eb8eb4-1ac6-4d47-9f7f-a07978cd4e6an%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/prometheus-users/97eb8eb4-1ac6-4d47-9f7f-a07978cd4e6an%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 prometheus-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/a07aac8d-f984-4619-baf0-b78ac87af378n%40googlegroups.com.

Reply via email to