A city telemetry service adds a Prometheus label for every client MAC and also stores raw Meraki response bodies inside distributed traces. After a week the metrics store is huge and traces contain PII. What observability design mistake does this illustrate?
Select an answer to reveal the explanation.
Short Explanation
Imagine putting a unique sticker on every grain of sand and shipping the whole beach in each letter—you drown the mailbox. A label per MAC and raw API bodies explode cardinality and leak data. Good design chooses what not to emit.
Full Explanation
High-cardinality labels (per MAC, per username) and embedding full API payloads in traces inflate storage and risk privacy exposure. Observability design for DEVCOR-style apps favors bounded labels and summarized fields so telemetry stays useful. Transport choice or paging channel is not the core issue here.