You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm tying to connect the jaeger-collector with an existing ElasticSearch cluster.
For the connection, the ElasticSearch requires a Pre-Shared Key to be send from the client (jaeger-collector) in a custom HTTP Header (e.g. X-INTERNET-PSK: xxx).
Is it possible to send a custom HTTP header from the jaeger-collector to ElasticSearch? How this can be achieved?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I'm tying to connect the jaeger-collector with an existing ElasticSearch cluster.
For the connection, the ElasticSearch requires a Pre-Shared Key to be send from the client (jaeger-collector) in a custom HTTP Header (e.g. X-INTERNET-PSK: xxx).
Is it possible to send a custom HTTP header from the jaeger-collector to ElasticSearch? How this can be achieved?
Many thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions