Skip to content

Commit 2578540

Browse files
committed
add tabs
1 parent 4037191 commit 2578540

File tree

1 file changed

+21
-9
lines changed

1 file changed

+21
-9
lines changed

solutions/observability/incident-management/create-a-failed-docs-rule.md

Lines changed: 21 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -24,33 +24,45 @@ Create a failed docs rule using the [custom threshold rule](../incident-manageme
2424
:screenshot:
2525
:::
2626

27-
To create a failed docs rule:
27+
When creating a failed docs rule, the process depends on your deployment type and your space's solution view. You can check your solution view by selecting the **Spaces** icon.
2828

29+
Select the appropriate tab for your setup, then follow the instructions to create a failed docs rule:
30+
31+
::::{tab-set}
32+
33+
:::{tab-item} Serverless and Observability view
2934
1. From the main menu, open the **Data Set Quality** page from **Management****Stack Management**, or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
3035
1. Find the data set you want to create a rule for in the table, and select **Open** from the **Actions** column.
31-
1. Select **Alerts****Create custom threshold rule**. If your space uses the the **Classic** solution view, you need to complete some extra steps after selecting **Alerts** before you continue. Refer to [Create a data view](#observability-create-failed-docs-data-view).
36+
1. Select **Alerts****Create custom threshold rule**.
3237
1. Select **Add aggregation/field**.
3338
1. For your new aggregation, set **Aggregation type** to **Count** and **KQL Filter** to `_index : ".fs*"`.
3439
1. Select **Equation**, and set the equation to `(B / A) * 100`.
3540
1. Set **Is above** to `1.5`.
3641
1. Set the **Label** to `Failed docs`.
37-
1. Select **Next** to go to the **Details** menu.
38-
1. Set the **Rule name** to `Dataset quality` and add `failed_docs` to the **Tags**.
42+
1. Select **Next** to go to the **Details** step.
43+
1. Set the **Rule name** to `Data set quality` and add `failed_docs` to the **Tags**.
3944
1. Select **Create rule**.
45+
:::
4046

41-
## Create a data view [observability-create-failed-docs-data-view]
42-
43-
If your space uses the **Classic** solution view, you'll need to create a data view for your rule. After selecting **Alerts** in the previous section:
44-
47+
:::{tab-item} Classic solution view
4548
1. Select **Manage rules and connectors**.
4649
1. Select **Create rule**, then **Custom threshold**.
4750
1. Select **Data view**, then **Create a data view**.
4851
1. Find your data stream under **All sources**.
4952
1. Name your data view.
5053
1. Add your index pattern with `::failures` appended. For example, `logs-synth.2-default,logs-synth.2-default::failures`.
5154
1. Select **Save data view to Kibana**.
55+
1. Select **Add aggregation/field**.
56+
1. For your new aggregation, set **Aggregation type** to **Count** and **KQL Filter** to `_index : ".fs*"`.
57+
1. Select **Equation**, and set the equation to `(B / A) * 100`.
58+
1. Set **Is above** to `1.5`.
59+
1. Set the **Label** to `Failed docs`.
60+
1. Select **Next** to go to the **Details** menu.
61+
1. Set the **Rule name** to `Data set quality` and add `failed_docs` to the **Tags**.
62+
1. Select **Create rule**.
63+
:::
5264

53-
After saving your data view, follow the instructions in the previous section beginning with step 4 to finish creating your failed docs rule.
65+
::::
5466

5567
## Add actions [observability-create-failed-docs-alert-rule-add-actions]
5668

0 commit comments

Comments
 (0)