mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-04-03 13:58:56 +00:00
4da8f9fec7
This change adds the AlertActionManager and AlertActionEntry. The old AlertActionManager has become the AlertActionRegistry. This means that now the results of Alerts are queued up in a job queue and executed in separate threads. The AlertActionManager is a composite member of the AlertManager. Change the BasicTest to just run on a single node to fix the action registration if the action happens on a different node. Threads are not directly constructed but now the threadpool is used. The ClusterStateListener in AlertManager is responsible now for starting the job queue. Original commit: elastic/x-pack-elasticsearch@a73c6b60f8
26 lines
954 B
Java
26 lines
954 B
Java
/*
|
|
* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
|
|
* or more contributor license agreements. Licensed under the Elastic License;
|
|
* you may not use this file except in compliance with the Elastic License.
|
|
*/
|
|
package org.elasticsearch.alerts;
|
|
|
|
import org.elasticsearch.alerts.actions.AlertActionRegistry;
|
|
import org.elasticsearch.alerts.rest.AlertRestHandler;
|
|
import org.elasticsearch.alerts.scheduler.AlertScheduler;
|
|
import org.elasticsearch.alerts.triggers.TriggerManager;
|
|
import org.elasticsearch.common.inject.AbstractModule;
|
|
|
|
public class AlertingModule extends AbstractModule {
|
|
|
|
@Override
|
|
protected void configure() {
|
|
bind(AlertManager.class).asEagerSingleton();
|
|
bind(TriggerManager.class).asEagerSingleton();
|
|
bind(AlertScheduler.class).asEagerSingleton();
|
|
bind(AlertActionRegistry.class).asEagerSingleton();
|
|
bind(AlertRestHandler.class).asEagerSingleton();
|
|
}
|
|
|
|
}
|