nulogy_message_bus_consumer 0.3.2 → 1.0.0

data/lib/nulogy_message_bus_consumer/steps/monitor_replication_lag.rb

@@ -1,51 +0,0 @@
-module NulogyMessageBusConsumer
-  module Steps
-    class MonitorReplicationLag
-      def initialize(logger)
-        @logger = logger
-      end
-
-      def call(kafka_consumer:, **_)
-        # Ensure that the process is terminated if there is a problem getting the consumption lag.
-        # This also ensures that the process will terminate on-boot if it cannot connect to Kafka,
-        # allowing the container to be terminated by ECS.
-        Thread.abort_on_exception = true
-
-        Thread.new do
-          # Delayed start. If we attempt to read consumer#committed immediately, it may fail.
-          # We suspect this is because the consumer#committed is called before the consumer
-          # has finished connecting. There appears to be a race condition.
-          KafkaUtils.wait_for_assignment(kafka_consumer)
-
-          loop do
-            lag_per_topic = kafka_consumer.lag(kafka_consumer.committed)
-
-            @logger.info(JSON.dump({
-              event: "consumer_lag",
-              topics: Calculator.add_max_lag(lag_per_topic),
-            }))
-            STDOUT.flush
-
-            sleep 60
-          end
-        end
-
-        yield
-      end
-
-      module Calculator
-        def self.add_max_lag(lag_by_topic)
-          lag_by_topic.each_value do |lag_by_partition|
-            lag_by_partition[:_max] = lag_by_partition.values.max || 0
-          end
-
-          lag_by_topic[:_max] = lag_by_topic
-            .map { |_topic, lag_by_partition| lag_by_partition[:_max] }
-            .max || 0
-
-          lag_by_topic
-        end
-      end
-    end
-  end
-end