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
Describe the bug
I am currently using the Fluent Bit HTTP output plugin to send data to an OpenSearch endpoint. The configuration for the HTTP output includes a static URI as shown below:
[OUTPUT]
Name http
Match *
host opensearch
Port 9200
URI /test/_doc?routing=$routing
tls On
tls.verify Off
http_User admin
http_Passwd pwd
header Content-Type application/json; charset=utf-8
allow_duplicated_headers false
Format json_stream
In this setup, I need the routing value in the URI to be dynamically replaced based on the data being processed (i.e., extracted from each record). However, it seems that the URI field does not support dynamic placeholders, as the value remains empty or unchangeable at runtime.
Could you clarify:
Is it currently possible to use dynamic placeholders in the URI field?
If not, could this feature be considered for future releases?
The text was updated successfully, but these errors were encountered:
this is not supported. Note that the plugin receives a chunk that contains N records, if each recond have a different value for $routing you will need to do X number of HTTP requests. Maybe is easier to implement by using the Tag ?
Bug Report
Describe the bug
I am currently using the Fluent Bit HTTP output plugin to send data to an OpenSearch endpoint. The configuration for the HTTP output includes a static URI as shown below:
[OUTPUT]
Name http
Match *
host opensearch
Port 9200
URI /test/_doc?routing=$routing
tls On
tls.verify Off
http_User admin
http_Passwd pwd
header Content-Type application/json; charset=utf-8
allow_duplicated_headers false
Format json_stream
In this setup, I need the routing value in the URI to be dynamically replaced based on the data being processed (i.e., extracted from each record). However, it seems that the URI field does not support dynamic placeholders, as the value remains empty or unchangeable at runtime.
Could you clarify:
Is it currently possible to use dynamic placeholders in the URI field?
If not, could this feature be considered for future releases?
The text was updated successfully, but these errors were encountered: