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

Elastic Agent http_endpoint integration does not allow multiple include headers #6523

Closed
psanz-estc opened this issue Jun 9, 2023 · 2 comments · Fixed by #6548
Closed

Elastic Agent http_endpoint integration does not allow multiple include headers #6523

psanz-estc opened this issue Jun 9, 2023 · 2 comments · Fixed by #6548
Assignees

Comments

@psanz-estc
Copy link

In Elastic Agent http_endpoint integration there is a configuration called include_headers.

If you only set a single header here, it is working fine (e.g. only x-real-ip will add the headers.X-Real-Ip field in the indexed document).

As soon as you set multiple headers (e.g. x-real-ip and user-agent), it will not set any headers.* field.

image

That configuration translates into:

 - data_stream:
      dataset:user-events
    id: http_endpoint-http_endpoint.generic-ad5d8570-0456-11ee-a2d5-1234567890
    include_headers: user-agent,x-real-ip
    listen_address: 0.0.0.0
    listen_port: 8080
    pipeline: logs-user-events
    preserve_original_event: true

But as mentioned, the fields are not populated.

@elasticmachine
Copy link

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@efd6
Copy link
Contributor

efd6 commented Jun 13, 2023

That include_headers value doesn't look right, it should be a sequence, but instead the elements have been catted with a comma. This means that what filebeat will see is a single header "user-agent,x-real-ip". When the JSON API doc is requested, it does show up as an array.

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.

4 participants