Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISTIO stack enough? Can we do research on this/what’s missing #2

Open
durandom opened this issue Dec 10, 2020 · 1 comment
Open

Comments

@durandom
Copy link
Member

Is the #1 stack sufficient for initial projects?

@objectiser
Copy link

Currently Istio reports it's tracing data directly to a backend system, Jaeger being the default.

This may be good as an initial environment - as it would be possible for researchers to query the trace data from either Jaeger's query service, directly from the storage, or from a Kafka stream - depending upon how Jaeger is configured.

The downside is that this trace data would be in a Jaeger specific format.

As a future step we could provide additional instructions to configure OpenTelemetry collectors within this environment - this would enable research focused "processors" to be added to a custom OpenTelemetry Collector pipeline, and kafka stream based processing - but based on a "standard" (i.e. vendor neutral) trace data format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants