# Mixed type lumberjack {} input

**URL:** <https://discuss.elastic.co/t/mixed-type-lumberjack-input/1118>\
**Category:** Logstash\
**Created:** [May 21, 2015, 4:30pm UTC](https://discuss.elastic.co/t/mixed-type-lumberjack-input/1118 "2015-05-21T16:30:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Oneiroi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oneiroi/32/44793_2.png) [@Oneiroi](https://discuss.elastic.co/u/Oneiroi)\
**Post date:** [May 21, 2015, 4:30pm UTC](https://discuss.elastic.co/t/mixed-type-lumberjack-input/1118/1 "2015-05-21T16:30:53Z")

</div>

Currently have a single

```
input {
    lumberjack {
        port => 5XXXX
        ssl_certificate => "/logstash.crt"
        ssl_key => "/logstash.key"
        codec => json
    }
}

```

Currently however mixed types are being sent

- JSON logs (various)
- syslogs
- apache2 logs (access and error)
- nginx logs (access and error)

In 1.5.0 it has been noted that non JSON log types carry the tag: \_jsonparsefailure as a result.

As noted in [https://github.com/elastic/logstash/issues/3292#issuecomment-104336293](https://github.com/elastic/logstash/issues/3292#issuecomment-104336293) this configuration is suboptimal and slow down is expected.

As I understand it an "optimal" configuration from the logstash perspective is ot have multiple sources in the input section e.g.

port =\> 1234 - syslogs (no codec =\> json)  
port =\> 1235 - json logs ( codec =\> json)

and so on.

My question here is really, it is at all possible to have a single logstash-forwarder sending multiple log types and if so what configuration is required logstash side to avoid slow down but maintain the JSON parsing?

---

<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:** [July 6, 2017, 5:39am UTC](https://discuss.elastic.co/t/mixed-type-lumberjack-input/1118/2 "2017-07-06T05:39:30Z")

</div>