Skip to content

Commit 8868486

Browse files
authored
Remove article (#4765)
1 parent 4cfc56f commit 8868486

File tree

2 files changed

+0
-288
lines changed

2 files changed

+0
-288
lines changed

blog-cse/2023/12-31.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -247,8 +247,6 @@ The new index is automatically generated and retained for a period of 2 years at
247247

248248
As a result, the optional legacy Signal Forwarding feature in Cloud SIEM will be deprecated on **November 15, 2023**. Existing data will not be deleted, but new Signals generated after that date will no longer be forwarded using that feature and the option will no longer be available. (Signals will continue to be forwarded automatically to `sec_signal`.) Customers leveraging data forwarded using the legacy feature to generate dashboards (or for other use cases) will need to modify those applications to use the new `sec_signal` index before then. Note that the content of the `sec_signal` index is not identical to the content in data forwarded using the legacy option.
249249

250-
For more information about this change, and the differences between the two data sets, refer to our [2023 Cloud SIEM Signal Index Migration FAQ](/docs/cse/records-signals-entities-insights/signal-index-migration-faq/).
251-
252250

253251

254252
---

docs/cse/records-signals-entities-insights/signal-index-migration-faq.md

Lines changed: 0 additions & 286 deletions
This file was deleted.

0 commit comments

Comments
 (0)