Christoph Proeschel

Hi, we can reproduce this one quite consistently. With `1.2.0` we get this output: ``` [2018-04-09 17:26:53,496] [DEBUG] [TailThread-6] [Oplog:autoflush:107] Fsyncing /var/lib/mongodb-consistent-backup/default/20180409_1710/repl1/oplog-tailed.bson (secs_since=1.81, changes=6, ts=Timestamp(1523294813, 1)) [2018-04-09 17:26:54,645] [DEBUG] [TailThread-6]...

@ljupcovangelski The Kafka chart is bundled with the airy chart, right? In what scenario would the Kafka chart be installed in a different cluster? Or let me put it differently:...

@ljupcovangelski yes makes sense. Thanks for clarifying

I think the idea for the content is good, but "concepts" seems an even better section because this topic encapsulates unique learnings we made. So we could have it at...

@M-Shorouk Since #2753 is blocked by this I think it makes sense to start here: I want to better understand the nature of these contact events. What type of systems...

@AitorAlgorta understood. Then this is the same topic and I would still argue for treating these events as messages where the source is either `salesforce` or something like `salesforce_purchases`. If...

@AitorAlgorta We already have a salesforce connector that could take care of that. With events, the onus is shifted on the customer to maintain events. Merging _communication data_ with other...

# Events as messages proposal Given the above debate these events would be consumed as regular messages from a source such as salesforce purchase histories. For the sake of the...

@M-Shorouk I am not sure I understand: Does this mean the proposal works for you?

Thank you, @AitorAlgorta. As far as I understand these are advanced features of both the yet-to-be-built source implementation underlying these purchases (salesforce?) and of the messaging list in general.