@Nawab metrics.log*:- group=queue displays the data to be processed current_size can identify which queues are the bottlenecks blocked=true indicates a busy pipeline Checking metrics.log acros...
See more...
@Nawab metrics.log*:- group=queue displays the data to be processed current_size can identify which queues are the bottlenecks blocked=true indicates a busy pipeline Checking metrics.log across the topology reveals the whole picture. An occasional queue filling up does not indicate an issue. It becomes an issue when it remains full and starts to block other queues. index=_internal source=*metrics.log host=<your-hostname> group IN(pipeline, queue) 02-23-2019 01:08:43.802 +0000 INFO Metrics - group=queue, name=indexqueue, blocked=true, max_size_kb=500, current_size_kb=499, current_size=968, largest_size=968, smallest_size=968 02-23-2019 01:10:39.802 +0000 INFO Metrics - group=pipeline, name=typing, processor=sendout, cpu_seconds=0.05710199999999998, executes=134716, cumulative_hits=1180897