feat: Add development observability stack for testing OpenTelemetry with Jaeger, and Prometheus#101
feat: Add development observability stack for testing OpenTelemetry with Jaeger, and Prometheus#101morgan-wowk wants to merge 1 commit intomasterfrom
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
morgan-wowk
force-pushed
the
otel-observation
branch
from
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.
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.
Agreed. Folder is a bit too specific for the root dir.
Maybe something like
examples/setup/observability
morgan-wowk
force-pushed
the
otel-observation
branch
from
64467ae to
8713463
Compare
Volv-G
left a comment
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
morgan-wowk
force-pushed
the
otel-observation
branch
from
8713463 to
a3d924b
Compare
morgan-wowk
changed the title
morgan-wowk
force-pushed
the
otel-observation
branch
from
a3d924b to
7e12bb4
Compare
morgan-wowk
force-pushed
the
otel-api-tracing
branch
from
6041ed7 to
a12aa86
Compare
morgan-wowk
changed the base branch from
otel-api-tracing
to
graphite-base/101
morgan-wowk
force-pushed
the
otel-observation
branch
from
7e12bb4 to
457241a
Compare
morgan-wowk
force-pushed
the
graphite-base/101
branch
from
a12aa86 to
f7913db
Compare
| @@ -0,0 +1,44 @@ | |||
| # OpenTelemetry Collector config: receive OTLP, export traces to Jaeger and metrics for Prometheus scrape. | |||
There was a problem hiding this comment.
Is there a reason why this file extension is .yaml, while the others are .yml?
| |----------|--------|-------------| | ||
| | `TANGLE_OTEL_EXPORTER_ENDPOINT` | `http://localhost:4317` | OTLP collector address (gRPC). Use `host.docker.internal:4317` if Tangle runs inside Docker. | | ||
| | `TANGLE_OTEL_EXPORTER_PROTOCOL` | `grpc` | Protocol for the exporter (default). This stack only accepts gRPC. | | ||
| | `TANGLE_ENV` | optional | Included in the service name (e.g. `tangle-development`). Default: `development`. | |
There was a problem hiding this comment.
Can you explain what this is for? Is service name what is displayed/searched for in the observability tools?
4 participants
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.