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

Add x-elastic-product-origin header to all places that make requests to Elasticsearch #1191

Closed
jsvd opened this issue Nov 12, 2024 · 2 comments · Fixed by #1195
Closed

Add x-elastic-product-origin header to all places that make requests to Elasticsearch #1191

jsvd opened this issue Nov 12, 2024 · 2 comments · Fixed by #1195
Assignees

Comments

@jsvd
Copy link
Member

jsvd commented Nov 12, 2024

The Logstash Elasticsearch output plugin makes HTTP requests to the following Elasticsearch endpoints:

GET /
HEAD /
GET /_license
POST _bulk?filter_path=..
HEAD /_index_template/<index_name>
PUT /_index_template/<index_name>
HEAD /<index_name>
PUT /<index_name>
GET /_ilm/policy/logstash-policy
PUT /_ilm/policy/logstash-policy
GET /_nodes/http (sniffing)

Notes:

parent setting no longer works (probably hasn't for a long time)

Each of these calls should include the x-elastic-product-origin header to the HTTP request made to Elasticsearch

@jsvd jsvd changed the title Add x-elastic-internal-origin header to all places that make requests to Elasticsearch in logstash-output-elasticsearch Add x-elastic-internal-origin header to all places that make requests to Elasticsearch Nov 12, 2024
@robbavey robbavey changed the title Add x-elastic-internal-origin header to all places that make requests to Elasticsearch Add x-elastic-product-origin header to all places that make requests to Elasticsearch Nov 22, 2024
@robbavey
Copy link
Contributor

Updated to correct the header name to x-elastic-product-origin

@donoghuc
Copy link
Contributor

donoghuc commented Dec 9, 2024

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.

3 participants