[collectd] MySQL collectd plugin replicaton client grant on *.*
smcracraft at me.com
Mon Oct 13 22:51:15 CEST 2014
Yes, I chart everything from collectd over to graphite and use Icinga to alarm on everything.
Icinga is better than Nagios. More active. An improved fork.
Anyway, where do the following live in collectd? (Otherwise, I have
to one-off each with the collectd "exec" plugin and that costs one
process per measurement during the running system... which is not scalable.
Does Florian need to be in on this? He offered to help.
Executed_Gtid_Set: 1709fc15-6903-11e3-af9f-06de0b35f7f1:1, e42edd38-2f71-11e3-b83b-02a15cb45f0d:1-487420351
On Oct 12, 2014, at 10:12 PM, "Pavel V." <pavel2000 at ngs.ru> wrote:
> Our test case is flatlining due to
> very low replication data need.
> The other 4 stats that we look
> at a lot:
> Retrieved_Gtid_Set: e42edd38-2f71-11e3-b83b-02a15cb45f0d:344269919-487420351
> Executed_Gtid_Set: 1709fc15-6903-11e3-af9f-06de0b35f7f1:1, e42edd38-2f71-11e3-b83b-02a15cb45f0d:1-487420351
> Slave_IO_Running: Yes
> Slave_SQL_Running: Yes
> Are these anywhere in the collectd mysql plugin or do you think
> collectd plugin exec will be needed?
Do you want to place these on charts?
I can imagine how the last two metrics will look, but two the first?
Maybe you need other tool like Nagios which will monitor replication process and send you
notifications if something will fail? Personally I'm using both Nagios and Collectd on my servers.
Pavel mailto:pavel2000 at ngs.ru
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the collectd