kibana/x-pack/plugins/stack_alerts
Matthew Kime 631c24abf4
[unified search] Query string input uses data views plugin directly instead of via deprecated data plugin reference (#143611)
* use data views plugin

* remove unneeded dependency

* use data views plugin

* fix type

* type fix

* supply dataViews as depedency

* supply dataViews as depeden
2022-10-20 07:15:33 -07:00
..
common [Response Ops] Allow _source field for ES DSL query rules (#142223) 2022-10-05 19:18:59 -04:00
public [unified search] Query string input uses data views plugin directly instead of via deprecated data plugin reference (#143611) 2022-10-20 07:15:33 -07:00
server [ResponseOps][Alerting] create new logger with tag for rule/connector type, for logger given to executors (#142121) 2022-10-17 15:33:06 -04:00
jest.config.js [jest] update config files to get coverage per plugin (#111299) 2021-09-09 08:14:56 +02:00
kibana.json [unified search] Query string input uses data views plugin directly instead of via deprecated data plugin reference (#143611) 2022-10-20 07:15:33 -07:00
README.md [RAC][Refactoring] Rename alerting types in triggers_actions_ui (#121107) 2021-12-17 18:35:05 +01:00
tsconfig.json [Unified search] Create unified search plugin (#127651) 2022-04-05 12:23:31 +05:00

stack_alerts plugin

This plugin provides alertTypes shipped with Kibana for use with the the alerting plugin. When enabled, it will register the alertTypes by the Stack in the alerting plugin, register associated HTTP routes, etc.

The plugin setup and start contracts for this plugin are the following type, which provides some runtime capabilities. Each built-in alertType will have it's own top-level property in the IService interface, if it needs to expose functionality.

export interface IService {
  indexThreshold: {
     timeSeriesQuery(params: TimeSeriesQueryParameters): Promise<TimeSeriesResult>;
  }
}

Each Stack RuleType is described in it's own README: