# Logstash overrides input tcp codec from JSON to JSON\_Lines

**URL:** <https://discuss.elastic.co/t/logstash-overrides-input-tcp-codec-from-json-to-json-lines/202375>\
**Category:** Logstash\
**Created:** [October 4, 2019, 6:54pm UTC](https://discuss.elastic.co/t/logstash-overrides-input-tcp-codec-from-json-to-json-lines/202375 "2019-10-04T18:54:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmalhan](https://avatars.discourse-cdn.com/v4/letter/d/c77e96/32.png) [@dmalhan](https://discuss.elastic.co/u/dmalhan)\
**Post date:** [October 4, 2019, 6:54pm UTC](https://discuss.elastic.co/t/logstash-overrides-input-tcp-codec-from-json-to-json-lines/202375/1 "2019-10-04T18:54:57Z")

</div>

My config file:

```
input {
    tcp {
        port => 5044
        codec => json
    }
}

```

Everytime I run logstash, I get the following in my startup logs:

> [INFO][logstash.inputs.tcp] Automatically switching from json to json\_lines codec {:plugin=\>"tcp"}

Is there something wrong in my config file which tells Logstash to override my codec choice and use a different codec? I'm running Logstash in a Docker container using Logstash V7.1.0

---

<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:** [November 1, 2019, 6:55pm UTC](https://discuss.elastic.co/t/logstash-overrides-input-tcp-codec-from-json-to-json-lines/202375/2 "2019-11-01T18:55:02Z")

</div>

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