various metrics reporting monitors are enabled by user via putting them in druid.monitoring.monitors property. However, org.apache.druid.client.cache.CacheMonitor is enabled (hardcoded) on brokers and historicals via MetricsModule.register(binder, CacheMonitor.class); in CliBroker and CliHistorical
We currently don't use caching in our cluster but all cache metrics are periodically reported via the emitter creating unnecessary noise in the logs (we use LoggingEmitter) . There is no way to disable these.
can we remove the hardcoding from CliBroker and CliHistorical , let user add org.apache.druid.client.cache.CacheMonitor to druid.monitoring.monitors if they need them like any other metrics monitor.
various metrics reporting monitors are enabled by user via putting them in
druid.monitoring.monitorsproperty. However,org.apache.druid.client.cache.CacheMonitoris enabled (hardcoded) on brokers and historicals viaMetricsModule.register(binder, CacheMonitor.class);inCliBrokerandCliHistoricalWe currently don't use caching in our cluster but all cache metrics are periodically reported via the emitter creating unnecessary noise in the logs (we use
LoggingEmitter) . There is no way to disable these.can we remove the hardcoding from
CliBrokerandCliHistorical, let user addorg.apache.druid.client.cache.CacheMonitortodruid.monitoring.monitorsif they need them like any other metrics monitor.