ES: Content type detection for rest requests is deprecated - 5.4.X

Elastic Stack Logstash
1

Hi everyone

  • Elasticsearch version: elasticsearch-5.4.3-1.noarch
  • Logstash version: logstash-5.4.3-1.noarch

Scenario IT: beaver -> REDIS -> Logstash -> ES
ELK is working properly. No issues apparently.

I know this is a bit popular topic lately. There are plenty of threads talking about that. However, I did not found any thread yet with the right solution or full information about the issue.

Probably is not very critical however is kind of annoying.

[2017-06-29T08:53:49,273][WARN ][o.e.d.r.RestController ] Content type detection for rest requests is deprecated. Specify the content type using the [Content-Type] header.

Less than 1 day of uptime produces almost 200MB of log.

I have to mention that I cannot update more my Logstash clients as I read in this thread:

https://discuss.elastic.co/t/content-type-detection-for-rest-requests-is-deprecated/85814

As I wrote above there are (I think) in the last stable version .

Our logstash conf looks like this:

input {
  redis {
    host => 'ecluster-cache.xxxxxxxx.com'
    data_type => 'list'
    key => 'logstash'
    type => 'logs'
    batch_count => 10
    threads => 32
  }
}
...
output {
  elasticsearch {
    index => "logstash-%{app}-%{+YYYY.MM.dd}"
    hosts =>  "ecluster.xxxxxxxxx.com:9200"
    flush_size => 5000
    routing => "hot"
  }

Nothing fancy. Any ideas?

Regards,

R

2

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