XML

Word

Printable

Activity Type:
Product / Portfolio Work
Story Points:
1
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Color Status:
Not Selected
Docs QE Status:
NEW
Documentation Type:

API, Deploy, Release Notes
QE Status:
NEW
Release Note Text:
This enhancement allows administrators to provide a set of custom headers when configuring log forwarding to an Elasticsearch cluster.
Release Note Type:
Enhancement
Intelligence Requested:
Market:

Sprint:
Logging - Sprint 277, Logging - Sprint 278, Logging - Sprint 281, Logging - Sprint 282

Summary

As a user of ClusterLogForwarder,
I want to define custom request headers
So I can use an Elasticsearch output to forward to VictoriaLogs

Acceptance Criteria

Verify custom header's are added to the request when spec'd for an Elasticsearch output
Verify the upstream API documentation is regenerated

1. What are the implications when using a bearer token auth? Do we need to restrict certain header keys or values?

links to