Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

elasticsearch output Content type detection for rest requests is deprecated #2997

Closed
maayankestler opened this issue Jul 10, 2017 · 1 comment · Fixed by #2999
Closed

elasticsearch output Content type detection for rest requests is deprecated #2997

maayankestler opened this issue Jul 10, 2017 · 1 comment · Fixed by #2999
Milestone

Comments

@maayankestler
Copy link

Bug report

Hi, I am using the elasticsearch output plugin and i see those warnings in the elasticsearch's logs every telegraf's interval(10s):

[2017-07-10T07:51:00,329][WARN ][o.e.d.r.RestController   ] Content type detection for rest requests is deprecated. Specify the content type using the [Content-Type] header.
[2017-07-10T07:51:10,318][WARN ][o.e.d.r.RestController   ] Content type detection for rest requests is deprecated. Specify the content type using the [Content-Type] header.
[2017-07-10T07:51:20,331][WARN ][o.e.d.r.RestController   ] Content type detection for rest requests is deprecated. Specify the content type using the [Content-Type] header.
[2017-07-10T07:51:30,337][WARN ][o.e.d.r.RestController   ] Content type detection for rest requests is deprecated. Specify the content type using the [Content-Type] header.

when i stop the telegraf service those warnings stop.
i think that this is a problem in the Elasticsearch client and can be fixed by update the client after this commit.
see also this issue.

System info:

Telegraf v1.3.3 (git: release-1.3 46db92a)
Elasticsearch v5.5.0
Ubuntu 16.04.2 LTS

@danielnelson
Copy link
Contributor

Thanks for tracking down the cause of this, I updated the elastic client and it will be in 1.4

@danielnelson danielnelson added this to the 1.4.0 milestone Jul 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants