Operators cannot tell which Cisco platform hop failed for a given city-portal request because the app only emits local print statements. What observability design set should the integration hop expose?
Select an answer to reveal the explanation.
Short Explanation
Print statements are sticky notes on one desk—they cannot answer which hop failed for this request. Observability means structured logs, per-client latency and error metrics, and a trace ID that follows the call. “We have logging” alone is not enough.
Full Explanation
Local print output cannot answer which hop failed for a request. Observability design for Cisco-API integration means structured logs, a latency or error metric per platform client, and a trace identifier that follows the call. Do not make AppDynamics the correct product answer here; that capability is covered under the Cisco Platforms domain, not this design-observability item.