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
Copy file name to clipboardExpand all lines: solutions/observability/streams/management/extract.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ If you edit the stream again, note the following:
71
71
- Changing existing processors or re-ordering them may cause unexpected results. Because the pipeline may have already processed the documents used for sampling, the UI cannot accurately simulate changes to existing data.
72
72
- Adding a new processor and moving it before an existing processor may cause unexpected results. The UI only simulates the new processor, not the existing ones, so the simulation may not accurately reflect changes to existing data.
73
73
74
-
74
+
75
75
76
76
### Ignore failures [streams-ignore-failures]
77
77
@@ -87,31 +87,31 @@ Documents fail processing for different reasons. Streams helps you to easily fin
87
87
88
88
In the following screenshot, the **Failed** percentage shows that not all messages matched the provided Grok pattern:
89
89
90
-
90
+
91
91
92
92
You can filter your documents by selecting **Parsed** or **Failed** at the top of the table. Select **Failed** to see the documents that weren't parsed correctly:
93
93
94
-
94
+
95
95
96
96
Failures are displayed at the bottom of the process editor:
These failures may require action, but in some cases, they serve more as warnings.
101
101
102
102
### Mapping conflicts
103
103
104
104
As part of processing, Streams also checks for mapping conflicts by simulating the change end to end. If a mapping conflict is detected, Streams marks the processor as failed and displays a failure message like the following:
Copy file name to clipboardExpand all lines: solutions/observability/streams/management/retention.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ applies_to:
9
9
10
10
Use the **Data retention** tab on the **Manage stream** page to set how long your stream retains data and to get insight into your stream's data ingestion and storage size.
11
11
12
-
12
+
13
13
14
14
The **Data retention** page is made up of the following components that can help you determine how long you want your stream to retain data:
15
15
@@ -30,15 +30,15 @@ The **Retention period** is the minimum number of days after which the data is d
30
30
1. Select **Edit data retention** → **Set specific retention days**.
31
31
1. From here, set the period of time you want to retain data for this stream.
32
32
33
-
To define a global default retention policy, refer to [project settings](../../../../../deploy-manage/deploy/elastic-cloud/project-settings.md).
33
+
To define a global default retention policy, refer to [project settings](../../../../deploy-manage/deploy/elastic-cloud/project-settings.md).
34
34
35
35
### Follow an ILM policy
36
36
```{applies_to}
37
37
stack: ga 9.1
38
38
```
39
-
[ILM policies](../../../../../manage-data/lifecycle/index-lifecycle-management.md) let you automate and standardize data retention across streams and other data streams. To have your streams follow an existing policy:
39
+
[ILM policies](../../../../manage-data/lifecycle/index-lifecycle-management.md) let you automate and standardize data retention across streams and other data streams. To have your streams follow an existing policy:
40
40
41
41
1. Select **Edit data retention** → **Use a lifecycle policy**.
42
42
1. Select a pre-defined ILM policy from the list.
43
43
44
-
You can also create a new ILM policy. Refer to [Configure a lifecycle policy](../../../../../manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md) for more information.
44
+
You can also create a new ILM policy. Refer to [Configure a lifecycle policy](../../../../manage-data/lifecycle/index-lifecycle-management/configure-lifecycle-policy.md) for more information.
Copy file name to clipboardExpand all lines: solutions/observability/streams/streams.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ applies_to:
5
5
---
6
6
7
7
:::{warning}
8
-
Streams is currently in Technical Preview and only available on Elastic Cloud Serverless deployments. This feature may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
8
+
Streams is currently in Technical Preview. This feature may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
9
9
:::
10
10
11
11
# Streams
@@ -29,12 +29,12 @@ In {{obs-serverless}}, Streams is automatically available.
29
29
30
30
In {{stack}} version 9.1 and later, you can enable Streams in the {{observability}} Advanced Settings. To do this:
31
31
32
-
1. Go to **Management** > **Stack Management** > **Advanced Settings**, or search for "Advanced Settings" in the [global search field](../../../../explore-analyze/find-and-organize/find-apps-and-objects.md).
32
+
1. Go to **Management** > **Stack Management** > **Advanced Settings**, or search for "Advanced Settings" in the [global search field](../../../explore-analyze/find-and-organize/find-apps-and-objects.md).
33
33
1. Enable **Streams UI** under **Observability**.
34
34
35
35
In {{serverless-short}} or after enabling Streams in {{stack}}, access the UI in one of the following ways:
36
36
37
-
- Select **Streams** from the navigation menu or use the [global search field](../../../../explore-analyze/find-and-organize/find-apps-and-objects.md).
37
+
- Select **Streams** from the navigation menu or use the [global search field](../../../explore-analyze/find-and-organize/find-apps-and-objects.md).
38
38
39
39
- From **Discover**, expand a document's details flyout and select **Stream** or an action associated with the document's data stream. Streams will open filtered to only the selected stream. This only works for documents stored in a data stream.
0 commit comments