Start here. This is the direct spoken answer to practice first.
Why this question matters
Define logs, metrics, traces, alerts, and dashboards needed to operate an ASP.NET Core API in production. It matters in real backend work because the team needs observability, ownership, and rollback room to recover without guessing. The practical angle is logs, metrics, traces, correlation, latency percentiles, dependency visibility, alert quality, and data-safety boundaries, tied to a concrete production decision.
I would expect structured logs, request metrics, dependency metrics, error tracking, and traces for important paths. At minimum, I want request count, status-code distribution, error rate, p95/p99 latency, and dependency duration for SQL, cache, and external calls. I also want correlation IDs. Without those, production debugging becomes guessing.