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
Which version of the demo you are using? (please provide either a specific commit hash
Symptom
The bug is present in the OTEL metrics schema present in the data-prepper pipeline. This schema is different from the one released in the opensearch catalog metrics schema
current mapping in the OS after running the demo is as below:
What is the expected behavior?
The main attributes of the metrics like serviceName, traceId and spanId should be keyword and not text datatype with the separate keyword mapping.
What is the actual behavior?
As mentioned above the current schema has serviceName, traceId and spanId with text mappings
Reproduce
Provide the minimum required steps to result in the issue you're observing.
Run the OTEL demo as is and see the mappings of the ss4o_metrics index.
Additional Context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Bug Report
Which version of the demo you are using? (please provide either a specific
commit hash
Symptom
The bug is present in the OTEL metrics schema present in the data-prepper pipeline. This schema is different from the one released in the opensearch catalog metrics schema
current mapping in the OS after running the demo is as below:
What is the expected behavior?
The main attributes of the metrics like serviceName, traceId and spanId should be keyword and not text datatype with the separate keyword mapping.
What is the actual behavior?
As mentioned above the current schema has serviceName, traceId and spanId with text mappings
Reproduce
Provide the minimum required steps to result in the issue you're observing.
Run the OTEL demo as is and see the mappings of the
ss4o_metrics
index.Additional Context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: