Description
Component(s)
exporter/opensearch
Describe the issue you're reporting
Hello,
I understand this component is no longer maintained but maybe someone can indicate what the initial design goals were as the generated trace data cannot be visualized with the OpenSearch Dashboard Trace Analytics plug-in . I read the following information and got a bit confused:
• The Opensearch exporter code stores telemetry data under indexes called ss4o-* according to the documentation here opentelemetry-collector-contrib/exporter/opensearchexporter at main · open-telemetry/opentelemetry-collector-contrib and opensearch-catalog/docs/schema/observability at main · opensearch-project/opensearch-catalog
• This issue [RFC] Observability indices naming standards & routing · Issue #1405 · opensearch-project/observability indicates an objective to standardize index naming under sso* indexes
• Data prepper code does not currently support ss4o according to Simple Schema for Observability - OpenSearch Documentation
So can anyone confirm the following:
• ss4o* is the targeted index naming pattern (and not sso*)
• ss40 is currently not supported by the OpenSearch Trace analytics UI plug-in. The plan is to add it as a new data source (in addition to Jaeger and Data Prepper).
• Data Prepper will evolve to support the ss40
Br
/Vincent