You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 16, 2022. It is now read-only.
Copy file name to clipboardExpand all lines: docs/alerting/index.md
-3Lines changed: 0 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,6 @@ Kibana
11
11
12
12
The alerting feature notifies you when data from one or more Elasticsearch indices meets certain conditions. For example, you might want to notify a [Slack](https://slack.com/) channel if your application logs more than five HTTP 503 errors in one hour, or you might want to page a developer if no new documents have been indexed in the past 20 minutes.
13
13
14
-
Monitors run as the `admin` user, which means that monitors can query all documents in all indices and do not consider the roles of the user who created the monitor. If your cluster contains sensitive data, we recommend [removing the alerting plugin](../install/plugins/#remove-plugins).
15
-
{: .warning }
16
-
17
14
To get started, choose **Alerting** in Kibana.
18
15
19
16

To install Alerting, you must first install the Job Scheduler plugin. Alerting has a corresponding [Kibana plugin](../../kibana/plugins) that you probably want to install as well.
@@ -237,14 +237,14 @@ To install Alerting, you must first install the Job Scheduler plugin. Alerting h
To install Index State Management, you must first install the Job Scheduler plugin. ISM has a corresponding [Kibana plugin](../../kibana/plugins) that you probably want to install as well.
This plugin lets you combine Kibana visualizations and narrative text in a single interface.
121
+
122
+
113
123
## List installed plugins
114
124
115
125
To check your installed plugins:
@@ -125,7 +135,13 @@ sudo bin/kibana-plugin list
125
135
sudo bin/kibana-plugin remove <plugin-name>
126
136
```
127
137
128
-
Then restart Kibana. After the removal of any plugin, Kibana performs an "optimize" operation the next time you start it. This operation takes several minutes even on fast machines, so be patient.
138
+
For certain plugins, you must also remove the "optimze" bundle. Here is a sample command for the Anomaly Detection plugin:
Then restart Kibana. After the removal of any plugin, Kibana performs an optimize operation the next time you start it. This operation takes several minutes even on fast machines, so be patient.
Open Distro for Elasticsearch 1.11.0 renames the SQL Workbench plugin for Kibana to the Query Workbench.
11
+
12
+
Instead of incrementing the `opendistro_sql_workbench` version number, remove the plugin and install `opendistro-query-workbench` instead, as covered in [Standalone Kibana plugin install](../../kibana/plugins/).
0 commit comments