Skip to content

Webtoon · EP01

Where Did the Order Go Wrong?

Follow a checkout failure to see why JENNIFER Kubernetes starts with application performance and brings in Kubernetes resource monitoring.

Materi ini tersedia dalam bahasa Inggris. Versi bahasa Indonesia belum tersedia.

JENNIFER KUBERNETES · FIELD NOTES WEBTOON EP01

Where Did the Order Go Wrong?

A checkout failure shows how JENNIFER Kubernetes brings application performance and Kubernetes resources into the same investigation.

01 A name that raises a question

Sam: So this just monitors pods and nodes? Justin: We monitor those too. But we start with the app.

02 A customer can’t place an order

A customer taps the order button on a phone. The checkout returns an error. Sam: A few customers can’t finish their orders. Justin: Let’s check the order requests first.

03 Start with the application

The Order API chart shows request errors increasing at 2:10. Sam: There. Order requests started failing at 2:10. Justin: What was happening to the pods running the order service then?

04 Check what the pods were doing

Sam studies the same time window. Two pods in the order service repeatedly restarted after 2:10. Sam: These pods kept restarting right when order errors spiked. Justin: Now we know where to look. Let’s find out why they restarted.

05 Put the signals on the same timeline

Sam and Justin line up the request errors and pod restarts at 2:10. The timing tells them where to investigate. Sam: The errors tell us what customers saw. The pod restarts tell us where to look. Justin: Right. Apps run on Kubernetes resources. Seeing both helps us track down the cause.

06 APM with Kubernetes context

Sam and Justin are back by the JENNIFER Kubernetes display. Philip quietly peeks out from under a desk. Sam: So it’s APM for apps running on Kubernetes. Justin: Exactly. We added Kubernetes monitoring to help you find where a problem starts.