33d50fb91e
Some checks failed
API CI / API Lint (push) Successful in 47s
API CI / API Type Check (push) Failing after 47s
API CI / API Test (push) Successful in 1m0s
API CI / API Build (push) Failing after 50s
API CI / Build Docker Image (push) Has been skipped
Build Crossplane Provider / build (push) Failing after 5m51s
CD Pipeline / Deploy to Staging (push) Failing after 29s
CI Pipeline / Lint and Type Check (push) Failing after 36s
CI Pipeline / Build (push) Has been skipped
CI Pipeline / Test Backend (push) Failing after 1m33s
CI Pipeline / Test Frontend (push) Failing after 30s
CI Pipeline / Security Scan (push) Failing after 1m16s
Crossplane Provider CI / Go Test (push) Failing after 3m23s
Crossplane Provider CI / Go Lint (push) Failing after 7m27s
Crossplane Provider CI / Go Build (push) Failing after 3m27s
Deploy to Staging / Deploy to Staging (push) Failing after 30s
Portal CI / Portal Lint (push) Failing after 21s
Portal CI / Portal Type Check (push) Failing after 21s
Portal CI / Portal Test (push) Failing after 21s
Portal CI / Portal Build (push) Failing after 22s
Test Suite / frontend-tests (push) Failing after 30s
Test Suite / api-tests (push) Failing after 49s
Test Suite / blockchain-tests (push) Failing after 30s
Type Check / type-check (map[directory:. name:root]) (push) Failing after 23s
Type Check / type-check (map[directory:api name:api]) (push) Failing after 21s
Type Check / type-check (map[directory:portal name:portal]) (push) Failing after 19s
Validate Configuration Files / validate (push) Failing after 1m52s
CD Pipeline / Deploy to Production (push) Has been skipped
Co-authored-by: Cursor <cursoragent@cursor.com>
1.7 KiB
1.7 KiB
Phoenix Observability Stack
Category: PLATFORM_SERVICES
Publisher: Phoenix Cloud Services
Status: PUBLISHED
Version: 1.0.0
Overview
Phoenix Observability Stack provides comprehensive observability with distributed tracing, structured logs with correlation IDs, and SLO monitoring. Features OpenTelemetry integration, distributed tracing across services, and SLOs for ledger posting, message delivery, and transaction settlement.
Key Features
- Distributed tracing: End-to-end request tracking
- OpenTelemetry integration: Standard observability protocol
- Structured logging: JSON logs with correlation IDs
- SLO monitoring: Service level objective tracking
- Metrics collection: Prometheus-compatible metrics
- Alerting: Configurable alerting rules
- Correlation IDs: Request correlation across services
API Endpoints
Get Traces
GET /observability/traces?correlationId=req_123&serviceName=ledger-service
Get Metrics
GET /observability/metrics?serviceName=ledger-service&metricName=request_rate&timeRange=1h
Get Logs
GET /observability/logs?correlationId=req_123&level=ERROR&limit=100
Get SLO Status
GET /observability/slos?serviceName=ledger-service&metricName=uptime
Pricing
- Model: Usage-based
- Per Metric: $0.0001
- Per Log: $0.00005
- Per Trace: $0.001
- Free Tier: 1,000,000 metrics/logs/month, 7-day retention
Compliance
- SOC 2 Type II
SLA
- Uptime: 99.9%
- Latency: <100ms p95
Architecture
- OpenTelemetry collectors
- Distributed tracing backend
- Log aggregation pipeline
- SLO calculation engine