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 believe this is the same issue as seen here: #8058
ES using dynamic mapping will read fields with "dots" as nested objects, causing the mapping conflicts. As far as I know this is on the ES side, and we're not able to build a payload with dotted fields that wouldn't end up nested.
vector 0.16.1
Vector Configuration File
Debug Output
Expected Behavior
Given 2 pods with label:
We send to elasticsearch in kubernetes.pod_labels.app:
{"kubernetes": {"pod_labels": {"app": "prometheus"}}}
{"kubernetes": {"pod_labels": {"app.kubernetes.io/instance": "prometheus-for-amp"}}}
Actual Behavior
It seems that we get:
We send to elasticsearch in kubernetes.pod_labels.app:
{"kubernetes": {"pod_labels": {"app": "prometheus"}}}
{"kubernetes": {"pod_labels": {"app": {"kubernetes": {"io/instance": "prometheus-for-amp"}}}}}
Additional Context
This results in elastic search:
for pod1 index schema is:
for pod2:
The text was updated successfully, but these errors were encountered: