ISTIOCTL-PROXY-CONFIG-LOG(1)

πŸ“¦ version 1.31.3, in nixos 26.05, nixpkgs unstable

πŸŽ€ ISTIOCTL-PROXY-CONFIG-LOG πŸŽ€

okay bestie, so the manual name here is istioctl-proxy-config-log, and this is the whole vibe: it grabs the logging levels of the Envoy hanging out inside whatever pod you point at πŸ’…


✨ NAME ✨

istioctl-proxy-config-log β€” retrieves logging levels of the Envoy in the specified pod πŸ¦‹


✨ SYNOPSIS ✨

istioctl proxy-config log [/][.] [flags]

✨ DESCRIPTION ✨

So basically: this pulls up the tea on the logging levels of the Envoy instance in the pod you specified β€” and yeah, it can update them optionally too, because we're multitasking queens πŸ‘‘ Get the info, or change the info, your call.


✨ OPTIONS ✨

  • -h, --help[=false] β€” help for log 🫢
  • --level="" β€” a comma-separated minimum per-logger level of messages to output, in the form of [:],[:],... β€” or leave it just that to change, like, all the active loggers 🌈 (you can list the logger components by running "istioctl proxy-config log " or by checking out https://github.com/envoyproxy/envoy/blob/main/source/common/common/logger.h, iykyk). And level can be one of [trace, debug, info, warning, error, critical, off] ⭐
  • -r, --reset[=false] β€” reset levels to default value (warning). fresh start energy 🧚
  • -l, --selector="" β€” label selector 🏷️

πŸ’œ OPTIONS INHERITED FROM PARENT COMMANDS πŸ’œ

  • --as="" β€” username to impersonate for the operation. User could be a regular user or a service account in a namespace 🫑
  • --as-group=[] β€” group to impersonate for the operation, this flag can be repeated to specify multiple groups.
  • --as-uid="" β€” UID to impersonate for the operation.
  • --context="" β€” Kubernetes configuration context 🌸
  • -i, --istioNamespace="istio-system" β€” Istio system namespace
  • --kubeclient-timeout="15s" β€” Kubernetes client timeout as a time.Duration string, defaults to 15 seconds. ⏰
  • -c, --kubeconfig="" β€” Kubernetes configuration file
  • -n, --namespace="" β€” Kubernetes namespace
  • -o, --output="short" β€” output format: one of json|yaml|short ✨
  • --proxy-admin-port=15000 β€” Envoy proxy admin port
  • --vklog=0 β€” number for the log level verbosity. Like -v flag. ex: --vklog=9 πŸ”₯

🌸 EXAMPLE 🌸

  # Retrieve information about logging levels for a given pod from Envoy.
  istioctl proxy-config log <pod-name[.namespace]>

  # Update levels of the all loggers
  istioctl proxy-config log <pod-name[.namespace]> --level none

  # Update levels of the specified loggers.
  istioctl proxy-config log <pod-name[.namespace]> --level http:debug,redis:debug

  # Reset levels of all the loggers to default value (warning).
  istioctl proxy-config log <pod-name[.namespace]> -r

no cap, that first one is literally just a vibe check on your logs πŸ‘€


🌈 SEE ALSO 🌈


ngl bestie, treat --reset with love β€” it's literally putting everything back to the default value (warning), so don't be surprised when the chatty logs go quiet πŸ™ˆ

and that's the whole page, periodt πŸŽ€ auto generated by spf13/cobra, dated Jan 1980, ISTIOCTL-PROXY-CONFIG-LOG(1) β€” mwah, ily, go read your logs πŸ’–πŸ¦‹βœ¨

πŸ“¦ where this page comes from