# Custom fields appear on different index or globally?

**URL:** <https://discuss.elastic.co/t/custom-fields-appear-on-different-index-or-globally/145688>\
**Category:** Elasticsearch\
**Created:** [August 23, 2018, 9:14am UTC](https://discuss.elastic.co/t/custom-fields-appear-on-different-index-or-globally/145688 "2018-08-23T09:14:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![geokal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geokal/32/29278_2.png) [@geokal](https://discuss.elastic.co/u/geokal)\
**Post date:** [August 23, 2018, 9:14am UTC](https://discuss.elastic.co/t/custom-fields-appear-on-different-index-or-globally/145688/1 "2018-08-23T09:14:04Z")

</div>

Hi, I have 2 pipelines with logstash for parsing diffent csv and on elasticsearch after indexing, custom fields which are created in one pipeline appear on every index or globally on "discover" and probably messes up the values fetched. Do I need a custom mapping on elastic or custom fields on one pipeline become globaly available thus appear on every index selected?

Thanks!!!

doing a GET /\_mapping returns the following:

```
 "stats-2018-08-22": {
"mappings": {
  "doc": {
    "properties": {
      "@timestamp": {
        "type": "date"
      },
      "@version": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "bytes_in/s": {
        "type": "long"
      },
      "bytes_out/s": {
        "type": "long"
      },
      "bytes_total": {
        "type": "long"
      },
      "column10": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "column11": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "column12": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "column13": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "column14": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "column15": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "column16": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "column6": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "column7": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "column8": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "column9": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "delay": {
        "type": "long"
      },
      "errors_in": {
        "type": "long"
      },
      "errors_out": {
        "type": "long"
      },
      "geoip": {
        "type": "object"
      },
      "host": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "interface": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "jitter": {
        "type": "long"
      },
      "loss": {
        "type": "long"
      },
      "message": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "packets_in": {
        "type": "long"
      },
      "packets_out": {
        "type": "long"
      },
      "packets_total": {
        "type": "long"
      },
      "path": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "pl": {
        "type": "float"
      },
      "rtt": {
        "type": "float"
      },
      "segment": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "tags": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "target_host": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "type": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      },
      "unix_timestamp": {
        "type": "text",
        "fields": {
          "keyword": {
            "type": "keyword",
            "ignore_above": 256
          }
        }
      }
    }
  }
}

```

}

why my custom fields from another pipeline ("jitter" "delay "loss") are presented on every index ?? as showed above

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 23, 2018, 10:44am UTC](https://discuss.elastic.co/t/custom-fields-appear-on-different-index-or-globally/145688/2 "2018-08-23T10:44:11Z")

</div>

Multiple files in the same directory are concatenated by Logstash, so all data will go to all output as described in[this thread](https://discuss.elastic.co/t/excess-data-in-elasticsearch/144860).

---

<div class="post-metadata">

**Author:** ![geokal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/geokal/32/29278_2.png) [@geokal](https://discuss.elastic.co/u/geokal)\
**Post date:** [August 23, 2018, 11:05am UTC](https://discuss.elastic.co/t/custom-fields-appear-on-different-index-or-globally/145688/3 "2018-08-23T11:05:16Z")

</div>

great!! thanks a lot for your rapid answer Christian!!!

---

<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:** [September 20, 2018, 11:05am UTC](https://discuss.elastic.co/t/custom-fields-appear-on-different-index-or-globally/145688/4 "2018-09-20T11:05:16Z")

</div>

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