Getting Started - PaaS Full Observability
This feature is currently being tested internally and is not yet available. The documentation here describes the planned functionality. We'll announce when it's ready for use.
If you want the complete observability experience - logs, metrics, and traces - you can instrument your application with OpenTelemetry and send data via OTLP.
What OTLP Gives You
Beyond basic logging, OpenTelemetry instrumentation provides:
- Metrics: Application-specific measurements (request counts, latencies, custom business metrics)
- Traces: Distributed tracing across services, showing request flows and timing
- Structured logs: Logs correlated with traces for easier debugging
Prerequisites
- Application running on Platon PaaS
- Tenant set up by Platon team (see PaaS Logging for how to request this)
Instrument Your Application
Add the OpenTelemetry SDK to your application. The exact steps depend on your language:
Configure the Exporter
Point your OTLP exporter to the in-cluster Alloy collector. Set these environment variables in your deployment:
env:
- name: OTEL_EXPORTER_OTLP_ENDPOINT
value: "http://alloy.alloy.svc.cluster.local:4317"
- name: OTEL_EXPORTER_OTLP_PROTOCOL
value: "grpc"
- name: OTEL_EXPORTER_OTLP_HEADERS
value: "tenant_id=your-tenant-name"
Replace your-tenant-name with your actual tenant name.
The tenant_id header is required. It determines which tenant your data belongs to. Without it, your data will be rejected.
Available Ports
| Protocol | Port | Use Case |
|---|---|---|
| OTLP gRPC | 4317 | Recommended (default) |
| OTLP HTTP | 4318 | When gRPC is not available |
View Your Data
Once instrumented:
- Logs: Explore → Select your Loki data source
- Metrics: Explore → Select your Mimir data source
- Traces: Explore → Select your Tempo data source
All three data sources are pre-configured in your Grafana organization.