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
+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
@@ -9,7 +9,7 @@ Extracting meaningful fields from your log messages lets you filter and analyze
9
9
10
10
From the **Processing** tab, you can add the [processors](#streams-extract-processors) you need to extract these structured fields. The UI then simulates your changes and provides an immediate [preview](#streams-preview-changes) that's tested end-to-end.
11
11
12
-
The UI also shows when you have indexing problems, such as [mapping conflicts](#streams-processing-mapping-conflicts), so you can address them before applying changes.
12
+
Streams also shows when you have indexing problems, such as [mapping conflicts](#streams-processing-mapping-conflicts), so you can address them before applying changes.
13
13
14
14
After creating your processor, all future ingested data will be parsed into structured fields accordingly.
15
15
@@ -135,6 +135,8 @@ Once saved, the processor provides a quick look at the processor's success rate
135
135
136
136
## Advanced: How and where do these changes get applied to the underlying data stream? [streams-applied-changes]
137
137
138
+
% make sure this is all still accurate.
139
+
138
140
When you save processors, Streams modifies the "best-matching" ingest pipeline for the data stream. In short, Streams either chooses the best-matching pipeline ending in `@custom` that is already part of your data stream, or it adds one for you.
139
141
140
142
Streams identifies the appropriate @custom pipeline (for example, `logs-myintegration@custom` or `logs@custom`).
@@ -169,6 +171,8 @@ You can still add your own processors manually to the `@custom` pipeline if need
169
171
170
172
## Known limitations [streams-known-limitations]
171
173
174
+
% update these limitations/verify limitations
175
+
172
176
- Streams does not support all processors. We are working on adding more processors in the future.
173
177
- Streams does not support all processor options. We are working on adding more options in the future.
174
178
- The data preview simulation may not accurately reflect the changes to the existing data when editing existing processors or re-ordering them.
0 commit comments