Skip to content

Commit

Permalink
Fix class used to initialize logger in Watcher (elastic#46467)
Browse files Browse the repository at this point in the history
This class has been using a logger configured for a different class for
quite a while. While the circumstance in which it logs is rare, it
should still use the correct logger.
  • Loading branch information
gwbrown authored Sep 10, 2019
1 parent 10da998 commit 7a2878b
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,8 @@
*/
package org.elasticsearch.xpack.watcher.execution;

import org.apache.logging.log4j.Logger;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;
import org.apache.logging.log4j.message.ParameterizedMessage;
import org.apache.logging.log4j.util.Supplier;
import org.elasticsearch.xpack.core.watcher.trigger.TriggerEvent;
Expand All @@ -16,7 +16,7 @@
import static java.util.stream.StreamSupport.stream;

public class AsyncTriggerEventConsumer implements Consumer<Iterable<TriggerEvent>> {
private static final Logger logger = LogManager.getLogger(SyncTriggerEventConsumer.class);
private static final Logger logger = LogManager.getLogger(AsyncTriggerEventConsumer.class);
private final ExecutionService executionService;

public AsyncTriggerEventConsumer(ExecutionService executionService) {
Expand Down

0 comments on commit 7a2878b

Please sign in to comment.