Where should we keep the example apps?

[mateuszrzeszutek]

Several repos (splunk-otel-java, splunk-otel-python) keep the example applications in the tracing-examples repo.
Several others (splunk-otel-java-lambda-wrapper, splunk-otel-js, splunk-otel-collector) keep them inside the repo in the examples/ directory.

Should we standardize that? Personally, I think that examples in the tracing-examples are very easily forgotten and can get out-of-date very easily, if we keep them in the main library repo it's easy to include the in the build process and keep them up-to-date.

[owais]

+1 for keeping them in the main repository. We can link from "tracing-examples" repo to these for sales/support engineers.

[MrAlias]

I think we can go with this approach. There is definitely benefit to having a centralized place to showcase examples for the reasons you mentioned. This will require a task be added to the release process for each repository to ensure the examples are kept up to date and build with the latest version of the released code.

We need to also make it clear that developer specific examples can be stored in the individual repositories. It is great to have generalized examples in the central repository, but we don't want to over-specify here and have users of these repositories short changed because we have made things unidiomatic for that language. As an example, the Go documentation renders examples which can also act as tests.

[ghost]

+1 for keeping examples in the main repository. This however will mean some (heavy) repos changes - in ideal world main structure should be:

• code (wrapper etc.)
• examples
  Also some examples from "tracing-examples" should be moved to appropriate repos.

[pellared]

We can always agree to follow this pattern for new splunk-otel-* repos. Rather than changing all repos such us signalfx-*-tracing.

[iNikem]

I don't understand what "heave repo changes" do you mean, @kubawach ?

[MrAlias]

We can always agree to follow this pattern for new splunk-otel-* repos. Rather than changing all repos such us signalfx-*-tracing.

FWIW the gdi-specification is only currently scoped to apply to splunk-otel-* repositories.

[pellared]

Shouldn't https://github.com/signalfx/microservices-demo be referenced in https://github.com/signalfx/tracing-examples

[ghost]

Another one that should join the pack of tracing examples: https://github.com/flands/spring-petclinic-microservices/tree/flands/opentelemetry

[ghost]

There are probably more - keeping those (eg related to splunk otel agent) in one place would GREATLY improve the situation.

[flands]

I believe one of the big benefits of the tracing-examples repository is that you can provide examples across languages. Is there any reason why each project cannot link to the central tracing-examples repository? I would like to propose we keep the same model.