forked from getlago/lago-api
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathkarafka.rb
30 lines (27 loc) · 1.35 KB
/
karafka.rb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
# frozen_string_literal: true
class KarafkaApp < Karafka::App
setup do |config|
config.kafka = { 'bootstrap.servers': ENV['LAGO_KAFKA_BOOTSTRAP_SERVERS'] }
config.client_id = 'Lago'
# Recreate consumers with each batch. This will allow Rails code reload to work in the
# development mode. Otherwise Karafka process would not be aware of code changes
config.consumer_persistence = !Rails.env.development?
end
# Comment out this part if you are not using instrumentation and/or you are not
# interested in logging events for certain environments. Since instrumentation
# notifications add extra boilerplate, if you want to achieve max performance,
# listen to only what you really need for given environment.
Karafka.monitor.subscribe(Karafka::Instrumentation::LoggerListener.new)
# Karafka.monitor.subscribe(Karafka::Instrumentation::ProctitleListener.new)
# This logger prints the producer development info using the Karafka logger.
# It is similar to the consumer logger listener but producer oriented.
Karafka.producer.monitor.subscribe(
WaterDrop::Instrumentation::LoggerListener.new(
# Log producer operations using the Karafka logger
Karafka.logger,
# If you set this to true, logs will contain each message details
# Please note, that this can be extensive
log_messages: false,
),
)
end