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
Replace leftover asciidoc lifecycle markers with applies_to (elastic#3143)
Reviewers, this PR:
- replaces the existing markers with what seems to be the most
appropriate equivalent applies_to
- removes a couple of markers that didn't feel appropriate or felt too
granular
Please check that the changes for the areas you own are correct, or
suggest edits where appropriate.
Note: some of those look really old, they may not be necessary anymore.
If you know about it, suggest to remove the applies_to.
Tip:
<img width="516" height="299" alt="image"
src="https://github.com/user-attachments/assets/5db29499-a9ea-4c89-bd65-c37587c54aea"
/>
Part of: elastic#2951
---------
Co-authored-by: Mike Birnstiehl <[email protected]>
Co-authored-by: David Kilfoyle <[email protected]>
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/alerts/alerting-common-issues.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ Configuration options are available to specialize connections to TLS servers, in
60
60
Rules are taking a long time to run and are impacting the overall health of your deployment.
61
61
62
62
::::{important}
63
-
By default, only users with a `superuser` role can query the [preview]{{kib}} event log because it is a system index. To enable additional users to run this query, assign `read` privileges to the `.kibana-event-log*` index.
63
+
By default, only users with a `superuser` role can query the {{kib}} event log because it is a system index. To enable additional users to run this query, assign `read` privileges to the `.kibana-event-log*` index.
[preview] In addition, there is a command-line client that uses legacy rule APIs, which can be easier to use, but must be updated for the new APIs. CLI tools to list, create, edit, and delete alerts (rules) and actions (connectors) are available in [kbn-action](https://github.com/pmuellr/kbn-action), which you can install as follows:
65
+
{applies_to}`stack: preview` {applies_to}`serverless: preview` In addition, there is a command-line client that uses legacy rule APIs, which can be easier to use, but must be updated for the new APIs. CLI tools to list, create, edit, and delete alerts (rules) and actions (connectors) are available in [kbn-action](https://github.com/pmuellr/kbn-action), which you can install as follows:
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/alerts/create-manage-rules.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ You can add one or more actions to your rule to generate notifications when its
61
61
62
62
Each action uses a connector, which provides connection information for a {{kib}} service or third party integration, depending on where you want to send the notifications.
63
63
64
-
[preview] Some connectors that perform actions within {{kib}}, such as the [Cases connector](kibana://reference/connectors-kibana/cases-action-type.md), require less configuration. For example, you do not need to set the action frequency or variables.
64
+
{applies_to}`stack: preview` {applies_to}`serverless: preview` Some connectors that perform actions within {{kib}}, such as the [Cases connector](kibana://reference/connectors-kibana/cases-action-type.md), require less configuration. For example, you do not need to set the action frequency or variables.
65
65
66
66
After you select a connector, set the action frequency. You can choose to create a summary of alerts on each check interval or on a custom interval. Alternatively, you an choose to run actions for each alert (at each check interval, only when the alert status changes, or at a custom interval).
67
67
@@ -129,7 +129,7 @@ When you snooze a rule, the rule checks continue to run on a schedule but alerts
129
129
130
130
When a rule is in a snoozed state, you can cancel or change the duration of this state.
131
131
132
-
[preview] To temporarily suppress notifications for rules, you can also create a [maintenance window](maintenance-windows.md).
132
+
{applies_to}`stack: preview` {applies_to}`serverless: preview` To temporarily suppress notifications for rules, you can also create a [maintenance window](maintenance-windows.md).
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/alerts/rule-types.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Some rule types are subscription features, while others are free features. For a
25
25
| --- | --- |
26
26
|[{{es}} query](rule-type-es-query.md)| Run a user-configured {{es}} query, compare the number of matches to a configured threshold, and schedule actions to run when the threshold condition is met. |
27
27
|[Index threshold](rule-type-index-threshold.md)| Aggregate field values from documents using {{es}} queries, compare them to threshold values, and schedule actions to run when the thresholds are met. |
28
-
|[{{transform-cap}} rules](../../transforms/transform-alerts.md)|[beta] Run scheduled checks on a {{ctransform}} to check its health. If a {{ctransform}} meets the conditions, an alert is created and the associated action is triggered. |
28
+
|[{{transform-cap}} rules](../../transforms/transform-alerts.md)|{applies_to}`stack: beta` {applies_to}`serverless: beta` Run scheduled checks on a {{ctransform}} to check its health. If a {{ctransform}} meets the conditions, an alert is created and the associated action is triggered. |
29
29
|[Tracking containment](geo-alerting.md)| Run an {{es}} query to determine if any documents are currently contained in any boundaries from a specified boundary index and generate alerts when a rule’s conditions are met. |
30
30
31
31
## {{observability}} rules [observability-rules]
@@ -38,8 +38,12 @@ If you create a rule in the {{observability}} app, its alerts are not visible in
38
38
::::
39
39
40
40
## Machine learning rules [ml-rules]
41
+
```{applies_to}
42
+
stack: beta
43
+
serverless: beta
44
+
```
41
45
42
-
[beta][{{ml-cap}} rules](../../machine-learning/anomaly-detection/ml-configuring-alerts.md) run scheduled checks on an {{anomaly-job}} to detect anomalies with certain conditions. If an anomaly meets the conditions, an alert is created and the associated action is triggered.
46
+
[{{ml-cap}} rules](../../machine-learning/anomaly-detection/ml-configuring-alerts.md) run scheduled checks on an {{anomaly-job}} to detect anomalies with certain conditions. If an anomaly meets the conditions, an alert is created and the associated action is triggered.
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/alerts/testing-connectors.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,11 @@ or by directly opening the proper connector edit flyout:
29
29
:screenshot:
30
30
:::
31
31
32
-
## [preview] Troubleshooting connectors with the `kbn-action` tool [_troubleshooting_connectors_with_the_kbn_action_tool]
32
+
## Troubleshooting connectors with the `kbn-action` tool [_troubleshooting_connectors_with_the_kbn_action_tool]
33
+
```{applies_to}
34
+
stack: preview
35
+
serverless: preview
36
+
```
33
37
34
38
You can run an email action via [kbn-action](https://github.com/pmuellr/kbn-action). In this example, it is a Cloud hosted deployment of the {{stack}}:
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/alerts/view-alerts.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ products:
13
13
14
14
When the conditions of a rule are met, it creates an alert. If the rule has actions, they run at the defined frequency. For example, the rule can send email notifications for each alert at a custom interval. For an introduction to the concepts of rules, alerts, and actions, refer to [Alerting](../alerts.md).
15
15
16
-
You can manage the alerts for each rule in **{{stack-manage-app}}** > **{{rules-ui}}**. Alternatively, manage all your alerts in **{{stack-manage-app}}** > **Alerts**.[preview]
16
+
You can manage the alerts for each rule in **{{stack-manage-app}}** > **{{rules-ui}}**. Alternatively, manage all your alerts in **{{stack-manage-app}}** > **Alerts**.
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/cases.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ products:
13
13
14
14
Cases are used to open and track issues directly in {{kib}}. You can add assignees and tags to your cases, set their severity and status, and add alerts, comments, and visualizations. You can create cases automatically when alerts occur or send cases to external incident management systems by configuring connectors.
15
15
16
-
You can also optionally add custom fields and case templates.[preview]
16
+
{applies_to}`stack: preview` {applies_to}`serverless: preview`You can also optionally add custom fields and case templates.
Copy file name to clipboardExpand all lines: explore-analyze/alerts-cases/cases/manage-cases.md
+2-6Lines changed: 2 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Open a new case to keep track of issues and share their details with colleagues.
23
23
:screenshot:
24
24
:::
25
25
26
-
2. If you defined [templates](manage-cases-settings.md#case-templates), you can optionally select one to use its default field values.[preview]
26
+
2. If you defined [templates](manage-cases-settings.md#case-templates), you can optionally select one to use its default field values.
27
27
3. Give the case a name, severity, and description.
28
28
::::{tip}
29
29
In the `Description` area, you can use [Markdown](https://www.markdownguide.org/cheat-sheet) syntax to create formatted text.
@@ -32,14 +32,10 @@ Open a new case to keep track of issues and share their details with colleagues.
32
32
4. Optionally, add a category, assignees, and tags. You can add users only if they meet the necessary [prerequisites](setup-cases.md).
33
33
5. If you defined any [custom fields](manage-cases-settings.md#case-custom-fields), they appear in the **Additional fields** section.
34
34
35
-
:::{admonition} Added in 8.15.0
36
-
This functionality was added in 8.15.0.
37
-
:::
38
-
39
35
6. For the **External incident management system**, select a connector. For more information, refer to [External incident management systems](manage-cases-settings.md#case-connectors).
40
36
7. After you’ve completed all of the required fields, click **Create case**.
41
37
42
-
[preview] Alternatively, you can configure your rules to automatically create cases by using [case actions](kibana://reference/connectors-kibana/cases-action-type.md). By default, the rule adds all of the alerts within a specified time window to a single case. You can optionally choose a field to group the alerts and create separate cases for each group. You can also choose whether you want the rule to reopen cases or open new ones when the time window elapses.
38
+
{applies_to}`stack: preview` {applies_to}`serverless: preview` Alternatively, you can configure your rules to automatically create cases by using [case actions](kibana://reference/connectors-kibana/cases-action-type.md). By default, the rule adds all of the alerts within a specified time window to a single case. You can optionally choose a field to group the alerts and create separate cases for each group. You can also choose whether you want the rule to reopen cases or open new ones when the time window elapses.
Copy file name to clipboardExpand all lines: explore-analyze/machine-learning/nlp/ml-nlp-elser.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ ELSER is an out-of-domain model which means it does not require fine-tuning on y
18
18
This model is recommended for English language documents and queries. If you want to perform semantic search on non-English language documents, use the [E5](ml-nlp-e5.md) model.
19
19
20
20
::::{important}
21
-
While ELSER V2 is generally available, ELSER V1 is in [preview]and will remain in technical preview.
21
+
While ELSER V2 is generally available, ELSER V1 is and will remain in technical preview.
0 commit comments