Studio journal
When metrics lie about API health
Green dashboards are soothing. Customers are not soothed by HTTP 200 responses that arrive after they have already abandoned the flow. Application analytics for microservices API experience must treat “healthy” as a product claim, not a status color.
The smiling success rate
Endpoints that always return 200 with an error payload, gateways that retry until something eventually works, and batch jobs that hide interactive failures — all inflate success. Pair status with time-to-useful-response and client-abandon signals.
Averages that erase evenings
Global averages dilute Busan dinner-hour congestion. Slice by region and by the customer moment. If you cannot afford infinite cardinality, at least keep a hand-picked set of slices on the analytics canvas.
Support tags as sensors
When “slow app” tickets rise while SLOs stay green, believe the tickets enough to investigate. In Service Signal Studio Module 5 we practice reconciling those contradictions in writing before touching config.