see
14:55:36 14:55:36.277 [pool-1-thread-1] DEBUG o.c.o.s.e.i.f.i.ActivityInstanceFetcher - Fetched [10000] historic activity instances within [269] ms 14:55:36 14:55:36.367 [pool-1-thread-1] DEBUG o.c.o.s.e.ElasticsearchImportJobExecutor - ElasticsearchImportJobExecutor: Currently active [0] jobs and [0] in queue 14:55:36 14:55:36.367 [pool-2-thread-1] DEBUG o.c.o.service.es.writer.EventsWriter - Writing [10000] events to elasticsearch 14:55:36 14:55:36.461 [pool-1-thread-1] DEBUG o.c.o.s.e.i.f.i.FinishedProcessInstanceFetcher - Fetched [1000] historic process instances within [94] ms 14:55:36 14:55:36.639 [pool-1-thread-1] DEBUG o.c.o.s.e.ElasticsearchImportJobExecutor - ElasticsearchImportJobExecutor: Currently active [1] jobs and [0] in queue 14:55:36 14:55:36.639 [pool-2-thread-2] DEBUG o.c.o.s.e.w.FinishedProcessInstanceWriter - Writing [1000] finished process instances to elasticsearch 14:55:36 14:55:36.639 [pool-1-thread-1] DEBUG o.c.o.s.e.ElasticsearchImportJobExecutor - ElasticsearchImportJobExecutor: Currently active [2] jobs and [0] in queue 14:55:36 14:55:36.639 [pool-1-thread-1] DEBUG o.c.o.s.e.i.f.i.VariableInstanceFetcher - fetching variables for [1000] PIs 14:55:36 14:55:36.750 [pool-1-thread-1] DEBUG o.c.o.s.e.i.f.i.VariableInstanceFetcher - Fetched [0] variables within [111] ms 14:55:37 14:55:36.775 [pool-2-thread-2] DEBUG o.c.o.s.es.writer.ImportIndexWriter - Writing import index to Elasticsearch 14:55:37 14:55:36.775 [pool-2-thread-2] DEBUG o.c.o.s.es.writer.ImportIndexWriter - Writing all entities based import index type [unfinished-process-instance-tracking] to elasticsearch. Starting from [29049] and having a max entity count [10837]
in this example
- pool-2 refers to ElasticsearchImportJobExecutor
- pool-1 refers to EngineImportJobExecutor
which is hard to determine without knowing internal structure of application. It could be more verbose if exact class names would be used for pool names
Nice idea for improvement! I like that you changed that