Hello Tao,
For your case maybe you can monitor the following jmx as well (see
http://kafka.apache.org/documentation.html#monitoring):
kafka.server:type=BrokerTopicMetrics,name=BytesOutPerSec
When a broker cannot properly respond to requests it will be much smaller
compared with other brokers.
Thanks Elias for sharing
On Mon, 29 Feb 2016 at 22:23 Elias Abacioglu <
elias.abacio...@deltaprojects.com> wrote:
> Crap, forgot to remove my signature.. I guess my e-mail will now get
> spammed forever :(
>
>
>
>
>
> On Mon, Feb 29, 2016 at 3:14 PM, Elias Abacioglu <
>
Crap, forgot to remove my signature.. I guess my e-mail will now get
spammed forever :(
On Mon, Feb 29, 2016 at 3:14 PM, Elias Abacioglu <
elias.abacio...@deltaprojects.com> wrote:
> We've setup jmxtrans and use it to check these two values.
> UncleanLeaderElectionsPerSec
>
We've setup jmxtrans and use it to check these two values.
UncleanLeaderElectionsPerSec
UnderReplicatedPartitions
Here is our shinken/nagios configuration:
define command {
command_name check_kafka_underreplicated
command_line $USER1$/check_jmx -U
Thanks Jens. What I want to achieve is to check every broker within a
cluster functions probably. The way you suggest can identify the liveness
of a cluster but it doesn't necessarily mean every broker in the cluster is
alive. In order to achieve that I can either create a topic with number of
Hi,
I assume you first want to ask yourself what liveness you would like to
check for. I guess the most realistic check is to put a "ping" message on
the broken and make sure that you can consume it.
Cheers,
Jens
On Fri, Feb 26, 2016 at 12:38 PM, tao xiao wrote:
> Hi
Hi team,
What is the best way to verify a specific Kafka node functions properly?
Telnet the port is one of the approach but I don't think it tells me
whether or not the broker can still receive/send traffics. I am thinking to
ask for metadata from the broker using consumer.partitionsFor. If it