Adrian Cole

my suspicions were correct. Zipkin correctly rejects malformed spans, so if any are in zipkin's indices, something else wrote them. We only support our schema for use in our collectors,...

See [this comment](https://github.com/openzipkin/zipkin/pull/3437#issuecomment-2011186880) as it is the same as for here. We cannot currently afford our own schema, so using data our collector intentionally rejects is outside the scope of...

@tacigar I rebased this for you. hope you have a chance to finish it!

I think if we want to support open search, we need a docker image for it. similar to https://github.com/openzipkin/zipkin/tree/master/docker/test-images/zipkin-elasticsearch7 Are you able to help create this? If not, let us...

I think it is easiest to make the image first in a separate PR. Then, merge and we can use it. I don't recall the history of the feature ask,...

@reta for the error around `ghcr.io/openzipkin/zipkin-opensearch2:3.3.1` you want to push a tag docker-3.3.1 off latest master. this will re-publish and also include the new one, unless we missed a spot...

also don't forget to set this public https://github.com/orgs/openzipkin/packages/container/zipkin-opensearch2/settings

@reta oh sorry.. I didn't remember what release was current. change the test code to use 3.3.0 and re-cut docker-3.3.0. that's the simplest way and will get the new test...

switched visibility to public ;) https://github.com/orgs/openzipkin/packages/container/zipkin-opensearch2/settings

when ready, re-prep the PR description, after making sure any markdown that need a usage example update have been so. Also, anything in general READMEs about things we test mention...