Open lgarvey opened 3 years ago
Facing the same issue with opensearch dashboard 1.2.0, and opensearch 1.2.3. In opensearch 1.1, where the tracing part is still a plugin, it worked. We only started seeing this issue after upgrading. My config & pipelines look pretty much identical to the above.
@bryanhonof , What version and distribution of Data Prepper are you using?
This GitHub project is the OpenDistro distribution of Data Prepper. It is no longer maintained and work have moved to the OpenSearch distribution of Data Prepper.
The latest version of OpenSearch Data Prepper is 1.2.1. You can read about migrating in the Migrating from OpenDistro page.
@bryanhonof , Do your services have interactions with each other? There is a ticket in OpenSearch Data Prepper to support the scenario where services do not interact with each other.
https://github.com/opensearch-project/data-prepper/issues/628
Does this sound like the issue you are experiencing?
What version and distribution of Data Prepper are you using?
@dlvenable We're currently using v1.2.1from dockerhub.
Do your services have interactions with each other?
They do yes.
Weird thing is that it only "disappeared" recently when we did and upgrade from opensearch 1.1 to, dasbhoard 1.2.0, and 1.2.3 for opensearch itself. Is there perhaps a migration step we missed? Because in 1.1 the tracing part of opensearch, if I'm not mistaken, was still a plugin.
Describe the bug The otel-v1-apm-service-map ES index is always empty, despite span data being received.
And data-prepper reporting that it has processed incoming data: "INFO com.amazon.dataprepper.pipeline.ProcessWorker - service-map-pipeline Worker: Processing 1 records from buffer"
Expected behavior I'd expect the
otel-v1-apm-service-map
to contain data, OR at least an error in either the data-prepper logs or the ES logs.Environment (please complete the following information): AES - 7.10 data-prepper 1.0 (docker) collector v0.29.0 (docker)
Additional context
data-prepper pipeline cofig:
collector config: