# Error in running Detection Rules Indicator Match

**URL:** <https://discuss.elastic.co/t/error-in-running-detection-rules-indicator-match/327853>\
**Category:** Elasticsearch\
**Tags:** detection-rules\
**Created:** [March 16, 2023, 12:47pm UTC](https://discuss.elastic.co/t/error-in-running-detection-rules-indicator-match/327853 "2023-03-16T12:47:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![viera120](https://avatars.discourse-cdn.com/v4/letter/v/74df32/32.png) [@viera120](https://discuss.elastic.co/u/viera120)\
**Post date:** [March 16, 2023, 12:47pm UTC](https://discuss.elastic.co/t/error-in-running-detection-rules-indicator-match/327853/1 "2023-03-16T12:47:59Z")

</div>

We are running Detection Rules to search for IOCs in firewall logs (using Indicator Matching). The firewall logs have a field named service. Every time there is a match the following error is seen:

```auto
Bulk Indexing of signals failed: object mapping for [service] tried to parse field [service] as object, but found a concrete value

```

Based on similar topics on this and other forums a solution offered is to rename the field (service).

The present index mapping for the field is:

```auto
"service": {
          "type": "text",
          "fields": {
            "keyword": {
              "type": "keyword",
              "ignore_above": 256
            }
          }
        }

```

Say we were to rename the field, is there a way to rename this field in the existing Elasticsearch indices (old data)?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 13, 2023, 12:48pm UTC](https://discuss.elastic.co/t/error-in-running-detection-rules-indicator-match/327853/2 "2023-04-13T12:48:16Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.