telescope
Telescope is a web-based log viewer that aggregates and visualizes logs from ClickHouse, StarRocks, Docker, and Kubernetes in a single unified interface. It provides filtering, search, time-range selection, and graph visualization capabilities with role-based access control via GitHub authentication.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | iamtelescope/telescope |
| Owner | iamtelescope |
| Primary language | Python |
| License | MIT — OSI-approved |
| Stars | 707 |
| Forks | 30 |
| Open issues | 12 |
| Latest release | v0.0.27 (2026-05-08) |
| Last updated | 2026-05-08 |
| Source | https://github.com/iamtelescope/telescope |
What telescope is
Python/Django backend with Vue.js frontend; supports structured log querying via ClickHouse/StarRocks SQL, ephemeral Docker/Kubernetes log retrieval, and RBAC-driven multi-tenancy. Currently at v0.0.27 in beta stage with incomplete features and potential stability concerns.
Get the telescope source
Clone the repository and explore it locally.
git clone https://github.com/iamtelescope/telescope.gitcd telescope# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires operational expertise to connect and configure ClickHouse or StarRocks backends; Docker/Kubernetes sources require API credentials and network access.
- Beta status means features may change, bugs may not be documented, and upgrade paths may require manual intervention or schema changes.
- GitHub-only authentication limits initial deployment to organizations using GitHub; other auth methods not available.
- RBAC and group-based access control add operational overhead for multi-tenant deployments but are essential for team-based use.
- Time-series query performance depends entirely on backend database tuning; Telescope is a UI layer with no built-in optimization.
When to avoid it — and what to weigh
- Production workloads requiring proven stability — Project is explicitly in beta stage with acknowledged bugs, incomplete features, and operational immaturity. Not recommended for critical production monitoring without thorough staging validation.
- Requirement for enterprise authentication (SAML, LDAP, etc.) — Currently limited to GitHub OAuth. SAML and other auth methods explicitly marked as non-required for v1.0.0, indicating no near-term support.
- Need for long-term log retention and compliance features — Snapshot storage for data loss prevention is still planned (not shipped). Audit logging is also planned, not available—unsuitable for audit-heavy compliance regimes.
- Requirement for live streaming or trailing logs — Live log trailing is a planned feature, not implemented. Use cases needing real-time log streaming should look elsewhere.
License & commercial use
MIT License—permissive, allows commercial use, modification, and distribution with attribution and warranty disclaimer.
MIT is a standard OSI-approved permissive license compatible with commercial use. However, no warranty is offered, and the project is in beta with acknowledged stability gaps. Evaluate risk tolerance against maturity level before relying on this in production services.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | Medium |
No security audit or vulnerability disclosure process mentioned. Beta status implies untested edge cases. GitHub OAuth setup required—ensure callback URLs and token scopes are verified. Direct database and API credentials passed to Telescope; audit who has access to the UI. No audit log yet—changes are untracked. Evaluate credential storage and transport in staging before production use.
Alternatives to consider
Grafana Loki + Grafana UI
Established, production-proven log aggregation with native Kubernetes support, Prometheus integration, and extensive enterprise features. Larger community, clearer upgrade path.
ELK Stack (Elasticsearch, Logstash, Kibana)
Industry-standard for centralized logging; mature, battle-tested, with strong multi-source support and comprehensive visualization. Higher operational overhead but proven in production at scale.
Datadog or New Relic Logs
SaaS observability platforms with built-in retention, audit, SAML, and compliance features. No self-hosting or backend tuning required, but vendor lock-in and recurring costs.
Build on telescope with DEV.co software developers
Evaluate Telescope in your staging environment. Assess beta maturity, backend connectivity, and GitHub OAuth setup for your observability stack.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
telescope FAQ
Is Telescope production-ready?
What databases are supported?
Can I use Telescope without GitHub authentication?
What is the deployment footprint?
Work with a software development agency
From first prototype to production, DEV.co delivers software development services around tools like telescope. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source observability and beyond.
Ready to unify your logs?
Evaluate Telescope in your staging environment. Assess beta maturity, backend connectivity, and GitHub OAuth setup for your observability stack.