# Reindexing to new index after doing some filter

**URL:** https://discuss.elastic.co/t/reindexing-to-new-index-after-doing-some-filter/377469
**Category:** Elasticsearch
**Tags:** elastic-stack-security, elastic-stack-alerting
**Created:** [April 24, 2025, 1:49am UTC](https://discuss.elastic.co/t/reindexing-to-new-index-after-doing-some-filter/377469 "2025-04-24T01:49:40Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![kulisiber](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kulisiber/32/141483_2.png) [@kulisiber](https://discuss.elastic.co/u/kulisiber)
#### Post date: [April 24, 2025, 1:49am UTC](https://discuss.elastic.co/t/reindexing-to-new-index-after-doing-some-filter/377469/1 "2025-04-24T01:49:40Z")

</div>

I would like to ask about ingest pipeline in Elastic SIEM. I'm a newbie here, sorry if I have a lot of questions. How to reindex from default index .kibana\_alerting\_cases\_8.15.0\_001 to a new index after filtering?

I've tried using chatgpt to figure that out, but from the ingest pipeline documentation and ChatGPT requires a "dest" processor, whereas on my elastic SIEM with version 8.15.0, the dest processor doesn't exist. Please for advice

Thanks