A parks department app polls Meraki for AP inventory and then parses the JSON locally. Operators need to know whether Meraki is slow or the parser is. Which observability design best answers that question?
Select an answer to reveal the explanation.
Short Explanation
Think of two stopwatches: one for the courier trip to Meraki and one for unpacking the box locally. Rate, errors, and duration on each hop tell you whether the platform or your code is the problem. Host CPU alone cannot make that call.
Full Explanation
Application design for Cisco API consumers includes per-dependency golden signals—request rate, error rate, and latency—so Meraki client behavior is separable from local parse work. Blended latency or host-CPU-only views hide which side degraded. Observability of each external dependency is part of the design, not an afterthought bolt-on.