Use this guide to diagnose and resolve common issues you may encounter while working with Workloads.
Understanding gaps in service maps
When viewing service dependency maps in Workloads, you may occasionally see visual gaps or disconnected service nodes. These breaks usually stem from trace sampling thresholds, missing telemetry along the transaction path, or unsupported entity types.
Common causes and fixes
Why downstream services appear disconnected
When an intermediate service in a trace fails to send span data, downstream services do not disappear from your workload — they appear as isolated fragments.
Because these downstream services successfully send trace context to New Relic, they remain visible in your workload. However, without span data from the missing parent service, they lose their visual anchor on the map and appear detached, along with any connected child services they manage.
To resolve disconnected downstream nodes, address the telemetry gap in the intermediate service using the steps above.