Roadmap updates per meeting this week #498
Conversation
This is an attempt to update and re-organize the roadmap. I am sure things are not where the maintainers would like them, so please comment and I will adjust accordingly. ## Which problem is this PR solving? Roadmap Updates ## Short description of the changes Re-organized existing roadmap, and added several items which are in active development today. Added more to the wish list and longer term goals. Signed-off-by: Jonah Kowall <jkowall@kowall.net>
|
Not sure what I did wrong on DCO, so please advise too :) |
The commands from the "Details" link should resolve this :) https://github.com/jaegertracing/documentation/pull/498/checks?check_run_id=2423531679 |
This is an attempt to update and re-organize the roadmap. I am sure things are not where the maintainers would like them, so please comment and I will adjust accordingly. ## Which problem is this PR solving? Roadmap Updates ## Short description of the changes Re-organized existing roadmap, and added several items which are in active development today. Added more to the wish list and longer term goals. Signed-off-by: Jonah Kowall <jkowall@kowall.net> Signed-off-by: Jonah Kowall <jkowall@gmail.com>
…ion-F Signed-off-by: Jonah Kowall <jkowall@kowall.net>
content/roadmap.md
Outdated
|
|
||
| [OpenTelemetry collector](https://opentelemetry.io/docs/collector/getting-started/) is a vendor-agnostic service for receiving, processing and exporting telemetry data. We have decided to rebuild the Jaeger backed components (agent, collector, ingester, all-in-one) on top of OpenTelemetry collector which has several benefits: | ||
| Aggregated trace metrics can be exported by the OpenTelemetry Collector [/opentelemetry-collector-contrib/tree/main/processor/spanmetricsprocessor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/spanmetricsprocessor) this allows metrics to be calculated off trace data and metrics to be exported from the Collector. We are adapting Jaeger to be able to read metrics from a Prometheus compatible backend, but additional backends may be supported. For additional information see [jaeger/pull/2946](https://github.com/jaegertracing/jaeger/pull/2946). |
There was a problem hiding this comment.
| Aggregated trace metrics can be exported by the OpenTelemetry Collector [/opentelemetry-collector-contrib/tree/main/processor/spanmetricsprocessor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/spanmetricsprocessor) this allows metrics to be calculated off trace data and metrics to be exported from the Collector. We are adapting Jaeger to be able to read metrics from a Prometheus compatible backend, but additional backends may be supported. For additional information see [jaeger/pull/2946](https://github.com/jaegertracing/jaeger/pull/2946). | |
| Aggregated trace metrics can be exported from the OpenTelemetry Collector by [spanmetricsprocessor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/spanmetricsprocessor) that allows metrics to be calculated from trace data. We are adapting Jaeger to be able to read metrics from a Prometheus compatible backend, but additional backends may be supported. For additional information see [jaeger/pull/2946](https://github.com/jaegertracing/jaeger/pull/2946). |
There was a problem hiding this comment.
It's better to link to an issue rather than pull request: jaegertracing/jaeger-ui#736
There was a problem hiding this comment.
That issue is for the UI, not the Otel processor. I linked to jaegertracing/jaeger#2954 which is the master issue for the UI change.
|
|
||
| * Multi-Tenancy ([mailgroup thread](https://groups.google.com/forum/#!topic/jaeger-tracing/PcxftflO4_o)) | ||
| * Cloud and Multi-DC strategy | ||
| * Anomaly detection of flagging of traces |
There was a problem hiding this comment.
I will show you a POC of the flagging in a forthcoming community meeting. We did a POC of this already. Just haven't discussed it yet :)
|
|
||
| * Multi-Tenancy ([mailgroup thread](https://groups.google.com/forum/#!topic/jaeger-tracing/PcxftflO4_o)) | ||
| * Cloud and Multi-DC strategy | ||
| * Anomaly detection of flagging of traces | ||
| * Baselining of trace metrics |
There was a problem hiding this comment.
Haven't discussed this one yet with you, but the idea would be to provide a proactive way to identify problems happening outside of a normal pattern. Building some basic baseline of the metrics and showing deviations. This is something Prometheus doesn't do today. It could belong as a Prometheus feature, but it depends how it's used inside Jaeger.
|
|
||
| * Multi-Tenancy ([mailgroup thread](https://groups.google.com/forum/#!topic/jaeger-tracing/PcxftflO4_o)) | ||
| * Cloud and Multi-DC strategy | ||
| * Anomaly detection of flagging of traces | ||
| * Baselining of trace metrics | ||
| * Alerting |
There was a problem hiding this comment.
hmmm... What kind of alerting (considering that you already have anomaly detection above)?
There was a problem hiding this comment.
Notifications, email/slack or maybe integrate with Alertmanager? I have some other ideas here potentially which I will bring up in a community call leveraging some of the OpenSearch capabilities which are plugins: https://opendistro.github.io/for-elasticsearch-docs/docs/alerting/ which might allow us to integrate. Of course these are all ideas we need to discuss.
Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
|
Botched this commit, so closing and replacing with #499 |
* Updates per discussion in #498 clarified several points Signed-off-by: Jonah Kowall <jkowall@kowall.net> * Update content/roadmap.md Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com> Signed-off-by: Jonah Kowall <jkowall@kowall.net> Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
This is an attempt to update and re-organize the roadmap. I am sure things are not where the maintainers would like them, so please comment and I will adjust accordingly.
Which problem is this PR solving?
Roadmap Updates
Short description of the changes
Re-organized existing roadmap, and added several items which are in active development today. Added more to the wish list and longer term goals.