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

Unable to send monitoring data due to 400 error from Elasticsearch bulk API #18786

Closed
ycombinator opened this issue May 27, 2020 · 3 comments · Fixed by #18787
Closed

Unable to send monitoring data due to 400 error from Elasticsearch bulk API #18786

ycombinator opened this issue May 27, 2020 · 3 comments · Fixed by #18787
Assignees

Comments

@ycombinator
Copy link
Contributor

Version: Filebeat 7.8.0, 8.0.0

Minimal Filebeat configuration:

filebeat.inputs:
- type: stdin

output.elasticsearch:
  hosts: [ "localhost:9200" ]

monitoring.enabled: true

When running this against any Elasticsearch 7.x or 8.0.0, Filebeat logs show the following errors:

2020-05-27T13:48:19.198-0400    ERROR   [publisher_pipeline_output]     pipeline/output.go:181  failed to publish events: 400 Bad Request: {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"request [/.monitoring-beats-7-2020.05.27/_bulk] contains unrecognized parameters: [system_api_version], [system_id]"}],"type":"illegal_argument_exception","reason":"request [/.monitoring-beats-7-2020.05.27/_bulk] contains unrecognized parameters: [system_api_version], [system_id]"},"status":400}

Note that this error is NOT observed with Filebeat 7.7.0.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations (Team:Integrations)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/stack-monitoring (Stack monitoring)

@ycombinator
Copy link
Contributor Author

I've narrowed down the commit that exposed this bug: 0575e15. That commit itself fixed another bug so we have to keep it. We just need to fix forward now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants