A citizen GIS lookup API is slow, but overall API duration mixes city code with a third-party GIS vendor. How should the developer instrument latency for clearer ownership?
Select an answer to reveal the explanation.
Short Explanation
When the whole request timer is one blob, you can't tell if city code or the GIS vendor is the slowpoke. Time the vendor hop on its own—custom metric or X-Ray subsegment—and ownership gets obvious. Then you tune the right side of the fence.
Full Explanation
Third-party dependency latency should be instrumented explicitly—via custom metrics or timed X-Ray subsegments—so operators can separate vendor delay from application processing time. Raising memory, hard-coding coordinates, or inferring latency from 4xx rates does not isolate external call performance. Explicit instrumentation enables targeted alarms and remediation for GIS integrations.