# IIS Logs

**URL:** <https://discuss.elastic.co/t/iis-logs/49711>\
**Category:** Logstash\
**Created:** [May 10, 2016, 11:51pm UTC](https://discuss.elastic.co/t/iis-logs/49711 "2016-05-10T23:51:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael1/32/29279_2.png) [@Michael1](https://discuss.elastic.co/u/Michael1)\
**Post date:** [May 10, 2016, 11:51pm UTC](https://discuss.elastic.co/t/iis-logs/49711/1 "2016-05-10T23:51:42Z")

</div>

Is it possible to have too large of IIS logs for Elasticsearch?

For example, there are at least ten servers sending IIS logs that are about 3GB each per file.

I have noticed today that IIS logs have not been in Kibana for the last few hours.

I do logstash logs | tail -n 50 and see the following ::

* * *

## 2016-05-10 23:47:09 +0000: HTTP parse error, malformed request (): #\<Puma::HttpParserError: Invalid HTTP format, parsing fails.\> 2016-05-10 23:47:09 +0000: ENV: {"rack.version"=\>[1, 3], "rack.errors"=\>#\<IO:fd 2\>, "rack.multithread"=\>true, "rack.multiprocess"=\>false, "rack.run\_once"=\>false, "SCRIPT\_NAME"=\>"", "CONTENT\_TYPE"=\>"text/plain", "QUERY\_STRING"=\>"", "SERVER\_PROTOCOL"=\>"HTTP/1.1", "SERVER\_SOFTWARE"=\>"2.11.3", "GATEWAY\_INTERFACE"=\>"CGI/1.2"}

## 2016-05-10 23:47:09 +0000: HTTP parse error, malformed request (): #\<Puma::HttpParserError: Invalid HTTP format, parsing fails.\> 2016-05-10 23:47:09 +0000: ENV: {"rack.version"=\>[1, 3], "rack.errors"=\>#\<IO:fd 2\>, "rack.multithread"=\>true, "rack.multiprocess"=\>false, "rack.run\_once"=\>false, "SCRIPT\_NAME"=\>"", "CONTENT\_TYPE"=\>"text/plain", "QUERY\_STRING"=\>"", "SERVER\_PROTOCOL"=\>"HTTP/1.1", "SERVER\_SOFTWARE"=\>"2.11.3", "GATEWAY\_INTERFACE"=\>"CGI/1.2"}

## 2016-05-10 23:48:09 +0000: HTTP parse error, malformed request (): #\<Puma::HttpParserError: Invalid HTTP format, parsing fails.\> 2016-05-10 23:48:09 +0000: ENV: {"rack.version"=\>[1, 3], "rack.errors"=\>#\<IO:fd 2\>, "rack.multithread"=\>true, "rack.multiprocess"=\>false, "rack.run\_once"=\>false, "SCRIPT\_NAME"=\>"", "CONTENT\_TYPE"=\>"text/plain", "QUERY\_STRING"=\>"", "SERVER\_PROTOCOL"=\>"HTTP/1.1", "SERVER\_SOFTWARE"=\>"2.11.3", "GATEWAY\_INTERFACE"=\>"CGI/1.2"}

## 2016-05-10 23:48:09 +0000: HTTP parse error, malformed request (): #\<Puma::HttpParserError: Invalid HTTP format, parsing fails.\> 2016-05-10 23:48:09 +0000: ENV: {"rack.version"=\>[1, 3], "rack.errors"=\>#\<IO:fd 2\>, "rack.multithread"=\>true, "rack.multiprocess"=\>false, "rack.run\_once"=\>false, "SCRIPT\_NAME"=\>"", "CONTENT\_TYPE"=\>"text/plain", "QUERY\_STRING"=\>"", "SERVER\_PROTOCOL"=\>"HTTP/1.1", "SERVER\_SOFTWARE"=\>"2.11.3", "GATEWAY\_INTERFACE"=\>"CGI/1.2"}

## 2016-05-10 23:49:09 +0000: HTTP parse error, malformed request (): #\<Puma::HttpParserError: Invalid HTTP format, parsing fails.\> 2016-05-10 23:49:09 +0000: ENV: {"rack.version"=\>[1, 3], "rack.errors"=\>#\<IO:fd 2\>, "rack.multithread"=\>true, "rack.multiprocess"=\>false, "rack.run\_once"=\>false, "SCRIPT\_NAME"=\>"", "CONTENT\_TYPE"=\>"text/plain", "QUERY\_STRING"=\>"", "SERVER\_PROTOCOL"=\>"HTTP/1.1", "SERVER\_SOFTWARE"=\>"2.11.3", "GATEWAY\_INTERFACE"=\>"CGI/1.2"}

I am seeing a LOT of these messages lately.

I also try logstash logs | grep "IIS" .........with no results found

---

<div class="post-metadata">

**Author:** ![Michael1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael1/32/29279_2.png) [@Michael1](https://discuss.elastic.co/u/Michael1)\
**Post date:** [May 11, 2016, 12:01am UTC](https://discuss.elastic.co/t/iis-logs/49711/2 "2016-05-11T00:01:33Z")

</div>

Also, here is a little bit of information about the ELK stack ::

4 Nodes

Node01 - 4 Cores 28 GB Memory  
Node02 - 4 Cores 28 GB Memory  
Node03 - 2 Cores 14 GB Memory  
Node04 - 2 Cores 14 GB Memory

Node01 and Node02 are "hot" nodes, which only keep logs for 5 days before moving them to the other two nodes, which are "warm" and "cold" nodes

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 11, 2016, 11:55pm UTC](https://discuss.elastic.co/t/iis-logs/49711/3 "2016-05-11T23:55:16Z")

</div>

> [@Michael1](#):
>
> 2016-05-10 23:49:09 +0000: ENV: {"rack.version"=\>[1, 3], "rack.errors"=\>#, "rack.multithread"=\>true, "rack.multiprocess"=\>false, "rack.run\_once"=\>false, "SCRIPT\_NAME"=\>"", "CONTENT\_TYPE"=\>"text/plain", "QUERY\_STRING"=\>"", "SERVER\_PROTOCOL"=\>"HTTP/1.1", "SERVER\_SOFTWARE"=\>"2.11.3", "GATEWAY\_INTERFACE"=\>"CGI/1.2"}

That looks like something that is not ES, do you have a load balancer somewhere?

---

<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, 4:58am UTC](https://discuss.elastic.co/t/iis-logs/49711/4 "2017-07-06T04:58:00Z")

</div>