Correlation
Service Relationships
Service edges come from parent/child spans and shared trace_id across service names you actually sent. Mydle does not invent a topology from traffic volume or clocks.
Observed edges
When spans in one trace_id carry different service values linked by parent_span_id, the product can show those observed relationships. Catalog ownership is separate from telemetry edges.
What is not a relationship
- Same approximate timestamp across services
- Similar latency or error rate
- Shared release or environment alone
- Platform mydle-web / mydle-worker ↔ customer services
Limitations
- Incomplete OTLP (sampled or single-service) yields incomplete graphs — by design.
- Declared service catalog dependencies are not auto-proven by telemetry unless IDs connect.