ISTIOCTL-EXPERIMENTAL-METRICS(1)

💅 istioctl-experimental-metrics — the metrics page, but make it a vibe

okay so real talk, this is the man page for istioctl-experimental-metrics, from the ISTIOCTL-EXPERIMENTAL-METRICS(1) manual. she's experimental, she's nosy, she wants to know how your workloads are doing. let's go 🫶

---

✨ NAME ✨

istioctl-experimental-metrics — Prints the metrics for the specified workload(s) when running in Kubernetes.

---

🌸 SYNOPSIS 🌸

istioctl experimental metrics ...

---

🦋 DESCRIPTION 🦋

okay so picture this: it Prints the metrics for the specified service(s) when running in Kubernetes. (yes, workload(s) up in NAME, service(s) down here — she contains multitudes, we move.)

bestie, here's the whole situation. This command finds a Prometheus pod running in the specified istio system namespace. iconic behavior. It then executes a series of queries per requested workload to find the following top-level workload metrics:

• total requests per second 🔥
• error rate 😭
• request latency at p50, p90, and p99 percentiles 📈

The query results are printed to the console, organized by workload name. cute, legible, slay.

⭐ important vibe check: All metrics returned are from server-side reports. This means that latencies and error rates are from the perspective of the service itself and not of an individual client (or aggregate set of clients). so like, it's the service's own POV, main character energy only. And — Rates and latencies are calculated over a time interval of 1 minute. one whole minute, no cap.

---

🎀 OPTIONS 🎀

• -d, --duration=1m0s — Duration of query metrics, default value is 1m. change it up if a minute isn't giving what you need 💅
• -h, --help[=false] — help for metrics. the classic. the blueprint. 🌈

💜 OPTIONS INHERITED FROM PARENT COMMANDS 💜

yep, she got these from her mom. still fully functional, still yours to use:

• --as="" — Username to impersonate for the operation. User could be a regular user or a service account in a namespace. living someone else's life, respectfully 🙈
• --as-group=[] — Group to impersonate for the operation, this flag can be repeated to specify multiple groups. stack 'em, collect 'em 🎀
• --as-uid="" — UID to impersonate for the operation.
• --context="" — Kubernetes configuration context. pick your universe ⭐
• -i, --istioNamespace="istio-system" — Istio system namespace. the default is literally istio-system, she's not trying to be mysterious.
• **--kubeclient-timeout="15s"** — Kubernetes client timeout as a time.Duration` string, defaults to 15 seconds. patience is a virtue but 15s is the limit, bestie 💀
• -c, --kubeconfig="" — Kubernetes configuration file.
• -n, --namespace="" — Kubernetes namespace.
• --vklog=0 — number for the log level verbosity. Like -v flag. ex: --vklog=9. she's chatty at 9, ngl 🔊

---

🧚 EXAMPLE 🧚

okay so here's how you actually run her, copy-paste ready:

# Retrieve workload metrics for productpage-v1 workload
istioctl experimental metrics productpage-v1

# Retrieve workload metrics for various services with custom duration
istioctl experimental metrics productpage-v1 -d 2m

# Retrieve workload metrics for various services in the different namespaces
istioctl experimental metrics productpage-v1.foo reviews-v1.bar ratings-v1.baz

the third one is the flex, fr fr — name.namespace dotted notation so you can check multiple namespaces in one go 👑

---

🔍 SEE ALSO 🔍

• istioctl-experimental(1) — go meet the whole experimental family, they're a lot 🫶

---

and that's the page!! 💖 Auto generated by spf13/cobra, dated Jan 1980 (yes bestie, 1980, she's vintage 👑), and the manual is ISTIOCTL-EXPERIMENTAL-METRICS(1). go query some metrics, you're gonna ate. ✨🌸💅