feat: Add development observability stack for testing OpenTelemetry with Jaeger, and Prometheus#101
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
1b51d55 to
64467ae
Compare
There was a problem hiding this comment.
Please add a bit more info on the purpose of these tools. It's not obvious that this is mostly for local testing.
There was a problem hiding this comment.
That sounds great. I changed the wording to "Development observability stack" and added the line "intended for local development testing"
There was a problem hiding this comment.
maybe rename the folder too? Alternatively, if we expect this folder to be filled with production telemetry tools in forked repos, we can somehow explain that.
There was a problem hiding this comment.
Thanks. I have renamed it to be an "example" and put emphasis on the fact that it is "intended as an example or for testing new telemetry data"
There was a problem hiding this comment.
Agreed. Folder is a bit too specific for the root dir.
Maybe something like
examples/setup/observability
64467ae to
8713463
Compare
Volv-G
left a comment
There was a problem hiding this comment.
I think we can proceed with this. If needed we can remove this later, but for the time being this seems to be a good tool to test new telemetry
8713463 to
a3d924b
Compare
a3d924b to
7e12bb4
Compare
6041ed7 to
a12aa86
Compare
7e12bb4 to
457241a
Compare
a12aa86 to
f7913db
Compare
examples/observability/otel-jaeger-prometheus/otel-collector-config.yaml
Show resolved
Hide resolved
457241a to
6e5bde4
Compare
Merge activity
|

Add development observability stack for testing OpenTelemetry with Jaeger, and Prometheus
TL;DR
Added a complete observability stack to collect and visualize traces and metrics from Tangle.
What changed?
otel-collector-config.yamlfor the OpenTelemetry Collectorprometheus.ymlfor PrometheusREADME.mdexplaining:How to test?
Why make this change?
This observability stack provides crucial visibility into Tangle's performance and behavior.