cameleer/cameleer-saas
2
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects Releases Wiki Activity

Phase 4: Observability Pipeline (was Phase 6) #28

New Issue
Closed
opened 2026-03-30 09:24:12 +02:00 by claude · 1 comment
claude commented 2026-03-30 09:24:12 +02:00
Owner
Copy Link

Overview

Connect cameleer3-server to customer app containers, enable tenant-scoped trace/metrics viewing via ClickHouse.

Architecture decision (2026-04-04): Moved from Phase 6 to Phase 4. ClickHouse replaced OpenSearch in the cameleer3-server stack. See docs/superpowers/specs/2026-04-04-dual-deployment-architecture.md.

Depends On

  • Phase 3 (#26 — Runtime Orchestration)

Related Epics

  • #6 (Observability Integration)

Key Deliverables

  • Agent → server connectivity — cameleer3-agent in customer containers connects to cameleer3-server
  • ClickHouse tenant-scoped data — partitioned by tenant_id (replaced OpenSearch)
  • Observability API proxy — tenant-aware routing to cameleer3-server via Traefik ForwardAuth
  • Basic topology graph — route structure from agent data
  • Agent ↔ server connectivity verification — health checks and diagnostics

Data Flow

Customer Camel App (with cameleer3-agent)
  → HTTP traces → cameleer3-server
  → ClickHouse (tenant-scoped storage)
  → API proxy (tenant-aware) → Frontend

PRD Reference

Section 9 (Observability Integration)
Superseded by: docs/superpowers/specs/2026-04-04-dual-deployment-architecture.md

## Overview Connect cameleer3-server to customer app containers, enable tenant-scoped trace/metrics viewing via ClickHouse. > **Architecture decision (2026-04-04):** Moved from Phase 6 to Phase 4. ClickHouse replaced OpenSearch in the cameleer3-server stack. See `docs/superpowers/specs/2026-04-04-dual-deployment-architecture.md`. ## Depends On - Phase 3 (#26 — Runtime Orchestration) ## Related Epics - #6 (Observability Integration) ## Key Deliverables - **Agent → server connectivity** — cameleer3-agent in customer containers connects to cameleer3-server - **ClickHouse tenant-scoped data** — partitioned by tenant_id (replaced OpenSearch) - **Observability API proxy** — tenant-aware routing to cameleer3-server via Traefik ForwardAuth - **Basic topology graph** — route structure from agent data - **Agent ↔ server connectivity verification** — health checks and diagnostics ## Data Flow ``` Customer Camel App (with cameleer3-agent) → HTTP traces → cameleer3-server → ClickHouse (tenant-scoped storage) → API proxy (tenant-aware) → Frontend ``` ## PRD Reference Section 9 (Observability Integration) Superseded by: `docs/superpowers/specs/2026-04-04-dual-deployment-architecture.md`
claude added the observabilityphase-6 labels 2026-03-30 09:24:47 +02:00
claude changed title from Phase 6: Observability Integration to Phase 4: Observability Pipeline (was Phase 6) 2026-04-04 14:39:54 +02:00
claude added phase-4 and removed phase-6 labels 2026-04-04 21:08:01 +02:00
claude commented 2026-04-04 21:08:11 +02:00
Author
Owner
Copy Link

Implementation PR: #34

Phase 4 delivers:

  • Observability dashboard via Traefik (/dashboard) — cameleer3-server React SPA
  • CAMELEER_TENANT_ID configured from CAMELEER_TENANT_SLUG env var
  • Inbound HTTP routing for customer apps (optional exposedPort, Traefik Host rules)
  • Agent status + observability status API endpoints
  • Startup connectivity check for cameleer3-server
  • No changes needed to cameleer3-server or agent code
Implementation PR: #34 Phase 4 delivers: - Observability dashboard via Traefik (`/dashboard`) — cameleer3-server React SPA - `CAMELEER_TENANT_ID` configured from `CAMELEER_TENANT_SLUG` env var - Inbound HTTP routing for customer apps (optional `exposedPort`, Traefik Host rules) - Agent status + observability status API endpoints - Startup connectivity check for cameleer3-server - No changes needed to cameleer3-server or agent code
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auth
Identity, authentication, OIDC, RBAC
 billing
Billing, metering, and Stripe integration
 day-1
Required for initial launch
 epic
Top-level epic grouping related issues
 future
Planned for future release
 infra
Infrastructure, GitOps, K8s orchestration
 licensing
License module and feature gating
 networking
Network isolation, VPN, tenant separation
 observability
Observability integration (cameleer3-server)
 ops
Platform operations and self-monitoring
 phase-1
Phase 1: Foundation + Auth
 phase-2
Phase 2: Tenants + Licensing
 phase-3
Phase 3: Runtime Orchestration + Environments
 phase-4
Phase 4: Observability Pipeline + Inbound Routing
 phase-5
Phase 5: K8s Operational Layer
 phase-6
Phase 6: Billing + Metering
 phase-7
Phase 7: Billing + Metering
 phase-8
Phase 8: Security Hardening + Self-Monitoring
 phase-9
Phase 9: Frontend (React Shell)
 platform
SaaS management platform
 runtime
Camel application runtime
 secrets
Secrets management and vault integration
 security
Security, compliance, SOC 2, audit
 task
Implementation task within a phase
No Label observability phase-4
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cameleer/cameleer-saas#28
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?