# traceway: OpenTelemetry-Native Observability in One Platform This repository profile is provided by osrepos.com, an open source repository discovery platform. Source: osrepos.com Repository profile: https://osrepos.com/repo/tracewayapp-traceway Generated for open source discovery and AI-assisted research. Traceway is an MIT-licensed observability platform built on OpenTelemetry, combining traces, logs, metrics, errors, session replay, and more. Self-host it with Docker Compose or use Traceway Cloud to investigate application issues in one place. GitHub: https://github.com/tracewayapp/traceway OSRepos URL: https://osrepos.com/repo/tracewayapp-traceway ## Summary Traceway is an MIT-licensed observability platform built on OpenTelemetry, combining traces, logs, metrics, errors, session replay, and more. Self-host it with Docker Compose or use Traceway Cloud to investigate application issues in one place. ## Topics - go - self-hosted - monitoring - observability - session-replay - on-call-paging ## Repository Information Last analyzed by OSRepos: Sat Oct 31 2026 01:03:31 GMT+0000 (Western European Standard Time) Detail views: 2 GitHub clicks: 0 ## Safety Notice OSRepos shares public repositories for knowledge and discovery only. Review source code, dependencies, licenses, and security implications before running or installing anything. ## Content ## Overview Traceway is an OpenTelemetry-native observability platform built on OpenTelemetry. It brings traces, logs, metrics, exceptions, session replay, AI tracing, and on-call paging together so teams can connect production signals and investigate problems without assembling a separate toolchain. Backend services send telemetry over OTLP/HTTP; browser and mobile apps use Traceway integrations. It is aimed at teams that want a unified observability service they can self-host or use through Traceway Cloud. The repository includes a Go backend, SvelteKit dashboard, CLI, agent skills, and examples. Its MIT license applies to the project, and the README describes its features as available without an open-core split. ## Key Features - Ingest OpenTelemetry traces, logs, and metrics over OTLP/HTTP, with trace-linked log search and span waterfalls. - Group exceptions by fingerprint and rank issues, with source maps and mobile symbolication support. - Track endpoint latency, throughput, and error rates, and define SLOs with error budgets and burn-rate alerts. - Capture session replays for web and mobile projects to provide context around errors. - Inspect AI usage, including token and cost data, latency, and conversations. - Configure on-call rotations, escalation policies, and notifications through supported channels. - Deploy with Docker Compose, use embedded Go mode, or choose the documented SQLite and DuckDB deployment options. - Use the read-only `traceway` CLI and agent skills to query telemetry; write access is a separate opt-in feature. ## Use Cases - An application team wants traces, logs, and metrics connected while diagnosing a production error. - A team shipping web or mobile apps needs to inspect the user session leading up to a crash or exception. - Platform engineers want to monitor endpoint performance and alert on service-level objectives. - Teams operating LLM-backed applications want visibility into AI request costs, tokens, latency, and conversations. - A Go developer wants to embed a lightweight observability backend in an application rather than deploy the standalone stack. ## Our Take Traceway is an actively maintained, broad OpenTelemetry-based observability option, with recent commits and releases, but its contribution history is concentrated around one contributor. **Good fit if:** - You want a self-hosted or managed platform that combines OpenTelemetry telemetry with errors, replay, and alerting. - Your services can report through OpenTelemetry and you want to avoid stitching together separate observability tools. - You value an MIT-licensed project and are comfortable evaluating a rapidly developed platform with concentrated contributions. **Look elsewhere if:** - Your environment depends on a specific integration or capability not listed in the repository documentation. - You need a project whose development is not heavily dependent on one contributor. - You do not want to operate a Docker Compose deployment or use the managed cloud option. ## Project Health | Signal | Value | |---|---| | Status | **Active**: regular commits and releases | | Last commit | 2026-10-29 (1 day ago) | | Commits, last 90 days | 100+ | | Releases, last 12 months | 100+ (latest cli/v2.0.8, 2026-10-28) | | Contributors | 18 (top contributor: 79% of commits) | | Issues closed, last 90 days | 35+ (typically closed in 7 days) | | Pull requests merged, last 90 days | 69 (typically merged in 1 day) | | Project age | 11 months | Checked on 2026-10-31 with the GitHub API. ## Project Facts - Language: Go - License: MIT - Stars: 1.8k - Forks: 92 - Topics: alerting, exception-tracker, issue-tracking, logs, metrics, monitoring, observability-platform, open-telemetry - Website: https://tracewayapp.com - Archived: no ## What You Need Detected in the repository: - Go (main language on GitHub) - A Dockerfile, so it can run in a container; a Compose file sets up the related services - A Helm chart for Kubernetes - Automated checks on GitHub Actions ## Getting Started ```bash git clone https://github.com/tracewayapp/traceway cd traceway && docker compose up -d ``` Open `http://localhost` and point an OpenTelemetry exporter at the local OTLP endpoint. See the [README](https://github.com/tracewayapp/traceway) and [self-hosting documentation](https://docs.tracewayapp.com/server/docker-compose) for configuration and production deployment details. ## License in Plain Words **MIT** (permissive). - Commercial use: yes - Modify and redistribute: yes - You must keep: the copyright and license notice - Share your changes: no A summary, not legal advice: the LICENSE file is what applies. ## Alternatives - [hertzbeat](https://osrepos.com/repo/apache-hertzbeat): HertzBeat focuses on agentless infrastructure and service monitoring, metrics, logs, and alerts rather than application traces, errors, and session replay. | Project | Language | License | Stars | Status | |---|---|---|---|---| | **traceway** | Go | MIT | 1.8k | Active | | [hertzbeat](https://osrepos.com/repo/apache-hertzbeat) | Java | Apache-2.0 | 7.4k | Active | ## Considerations - Project health is marked Active, with regular commits and releases and ongoing issue and pull-request handling. However, most reported code contributions come from one person, which is a contributor-concentration risk. - The recommended standalone setup uses Docker Compose and the documented stack includes ClickHouse and PostgreSQL. Embedded SQLite mode is available, with DuckDB as another documented option. - Profiling is explicitly described as experimental, so teams should assess its suitability before relying on it. - The README provides test commands, but the supplied requirements data does not indicate tests as a project requirement. Teams adopting it should assess the test coverage relevant to their deployment. - The repository is MIT licensed. Review the license and deployment documentation for your own distribution and operational requirements.