AI Architecture Analysis
This repository is indexed by RepoMind. By analyzing ymtdzzz/otel-tui in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Embed this Badge
Showcase RepoMind's analysis directly in your repository's README.
Repository Overview (README excerpt)
Crawler viewotel-tui A terminal OpenTelemetry viewer inspired by otel-desktop-viewer. This tool currently supports OpenTelemetry, Zipkin (Traces), Prometheus (Metrics), and Datadog (Traces, Metrics, Logs) formats. Traces Metrics Logs Getting Started Currently, this tool exposes the ports: • to receive OpenTelemetry signals (gRPC) • to receive OpenTelemetry signals (HTTP) • to receive Zipkin traces (enabled by option) • to receive Datadog signals (enabled by option) • to receive DogStatsD metrics (enabled by option) The server's Access-Control-Allow-Origin header includes , allowing telemetry to be sent directly from browser applications running on localhost. Options: Homebrew go install Docker Run in the container simply: Or, run as a background process and attach it: Docker Compose First, add service to your manifest ( ) for the instrumanted app Modify configuration for otelcol Run as a background process and attach it: Nix Executable Binary from Github Release page https://github.com/ymtdzzz/otel-tui/releases From Source Clipboard Functionality Requirements The clipboard feature ( key to copy log body) requires platform-specific tools: • **Linux/Unix**: Install or command • **macOS**: No additional tools required • **Windows**: No additional tools required **Note**: If clipboard tools are not available, the application will run normally but clipboard functionality will be disabled. TODOs There're a lot of things to do. Here are some of them: • Traces • [x] Display traces • [x] Filter traces • [x] Show trace information • Metrics • [x] Metric stream • [x] Display metric stream • [x] Filter metrics • [x] Show metric information • [ ] Display basic chart of the selected metric • [x] Gauge • [x] Sum • [x] Histogram • [ ] ExponentialHistogram • [ ] Summary • [ ] Metric list • [ ] Display metric stream • [ ] Flexible chart (query, selectable dimensions, etc.) • [ ] Auto refresh chart • [ ] Asynchronous chart rendering • Logs • [x] Display logs • [x] Filter logs • [x] Show log information • [x] Show logs related to a specific trace or span • UI • [ ] Improve UI • [ ] Add more keybindings • Performance • [x] Timer based refresh • [x] Data rotation (current buffer size: 1000 service root spans and logs) • Configurations • [x] Port • [ ] Refresh interval • [ ] Buffer size Contribution Contributions are always welcome! Whether it's reporting an issue, suggesting a feature, or submitting a pull request, your involvement is greatly appreciated. Below is a simple guide to help you get started. Creating a Pull Request Fork the Repository • Start by forking this repository to your GitHub account. Make Your Changes • Implement your changes in a new branch. Write Tests • Add tests to verify your changes. This helps ensure the stability of the project. Run Lint checks and Tests • Run the linting tools and test suite to verify your changes. Make sure everything passes before proceeding. Open a Pull Request • Push your branch to your forked repository. • Open a pull request to the main repository, providing a clear description of your changes and their purpose. Thank you for taking the time to contribute!