com.couchbase.client.dcp.metrics

Class DcpClientMetrics

java.lang.Object

com.couchbase.client.dcp.metrics.DcpClientMetrics

public class DcpClientMetrics
extends Object

Constructor Summary

Constructors

Constructor and Description
DcpClientMetrics(MetricsContext ctx)

Method Summary

Modifier and Type	Method and Description
DcpChannelMetrics	channelMetrics(HostAndPort address)
void	incrementAddChannel()
void	incrementReconfigure()
void	incrementRemoveChannel()
void	registerConnectionStatusGauges(Collection<DcpChannel> channels) Updates the "connection status" gauge for all channels.
LongAdder	scheduledPollingTasks()

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

DcpClientMetrics

public DcpClientMetrics(MetricsContext ctx)

Method Detail

incrementReconfigure

public void incrementReconfigure()

incrementAddChannel

public void incrementAddChannel()

incrementRemoveChannel

public void incrementRemoveChannel()

scheduledPollingTasks

public LongAdder scheduledPollingTasks()

channelMetrics

public DcpChannelMetrics channelMetrics(HostAndPort address)

registerConnectionStatusGauges

public void registerConnectionStatusGauges(Collection<DcpChannel> channels)

Updates the "connection status" gauge for all channels.

Micrometer gauges are finicky about only being registered once, which could cause problems if we were to naively register the gauge as part of the channel metrics, since it's possible for a channel to come and go.

A MultiGauge does not suffer from this limitation, so let's use that instead, and overwrite the previous measurements each time there's a connection state change. It's also an easy way to clean up gauges for channels that are no longer part of the cluster.