Skip to content

feat: Add development observability stack for testing OpenTelemetry with Jaeger, and Prometheus#101

Merged
morgan-wowk merged 1 commit intomasterfrom
otel-observation
Feb 25, 2026
Merged

feat: Add development observability stack for testing OpenTelemetry with Jaeger, and Prometheus#101
morgan-wowk merged 1 commit intomasterfrom
otel-observation

Conversation

@morgan-wowk
Copy link
Collaborator

@morgan-wowk morgan-wowk commented Feb 19, 2026

Add development observability stack for testing OpenTelemetry with Jaeger, and Prometheus

image.png

image.png

TL;DR

Added a complete observability stack to collect and visualize traces and metrics from Tangle.

What changed?

  • Added a Docker Compose setup with OpenTelemetry Collector, Jaeger, and Prometheus
  • Created configuration files for each component:
    • otel-collector-config.yaml for the OpenTelemetry Collector
    • prometheus.yml for Prometheus
  • Added comprehensive documentation in README.md explaining:
    • How to start and stop the stack
    • How to configure Tangle to export telemetry
    • Available UIs and ports
    • Troubleshooting common issues

How to test?

  1. Start the observability stack:
  2. Configure Tangle to export telemetry:
  3. Access the UIs:

Why make this change?

This observability stack provides crucial visibility into Tangle's performance and behavior.

Copy link
Collaborator Author

morgan-wowk commented Feb 19, 2026

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a bit more info on the purpose of these tools. It's not obvious that this is mostly for local testing.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That sounds great. I changed the wording to "Development observability stack" and added the line "intended for local development testing"

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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"

Copy link
Contributor

@Ark-kun Ark-kun Feb 20, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. Folder is a bit too specific for the root dir.
Maybe something like
examples/setup/observability

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like that

Copy link
Collaborator

@Volv-G Volv-G left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 morgan-wowk changed the title feat: Add optional OTel observation services (jaeger, prometheus) feat: Add development observability stack for testing OpenTelemetry with Jaeger, and Prometheus Feb 19, 2026
@morgan-wowk morgan-wowk changed the base branch from otel-api-tracing to graphite-base/101 February 20, 2026 01:53
@morgan-wowk morgan-wowk changed the base branch from graphite-base/101 to master February 20, 2026 01:56
Copy link
Contributor

@Ark-kun Ark-kun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, Morgan!

@morgan-wowk morgan-wowk merged commit 12cdfc6 into master Feb 25, 2026
2 checks passed
Copy link
Collaborator Author

Merge activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants