Debugging

Troubleshooting techniques for SEA™ Forge services.

Trace Analysis

1. Get trace ID from logs or headers
2. Search in OpenObserve: Traces → trace_id
3. Analyze span waterfall
4. Check for errors, high latency

Log Correlation

1
2
3
SELECT * FROM logs 
WHERE trace_id = '12345...'
ORDER BY _timestamp

Common Issues

No Telemetry Received

1. Check collector health: curl localhost:13133
2. Verify OTLP endpoint: localhost:4317
3. Check service SDK configuration

Missing Semantic Context

Ensure resource attributes are set:

1
2
3
4
resource = Resource.create({
    "sea.platform": "sea-forge",
    "sea.domain": "my-domain"
})

High Cardinality Warnings

Avoid high-cardinality labels:

1
2
3
4
5
# ❌ Bad
span.set_attribute("user.id", user_id)

# ✅ Good
span.set_attribute("user.tier", "premium")

Debug Commands

1
2
3
4
5
6
# Collector zpages
open http://localhost:55679/debug/tracez
open http://localhost:55679/debug/pipelinez

# Service health
curl http://localhost:8080/health

Last Updated: January 2026