In the example below, node-1 uses Kubernetes 1.19.6 and containerd 1.4.1.Find out what Kubernetes and container runtime are being used.Troubleshooting Kubernetes and container runtime incompatibility Version of Kubernetes and a container runtime that has been documented to beĬompatible. Kubernetes version and container runtime can vary, it is recommended to use a Runtimes such as containerd, CRI-O, Docker, and Marantis (formerly DockerĮngine – Enterprise) are well-supported. On each node in the cluster so that pods can run there. The Kubelet process on a node being in a defunct state.Containers, pods, and nodes failing to start successfully or stop cleanly.The Splunk OTel Collector that requires these stats will not produce the Stats from containers, pods, or nodes being absent or malformed.Possible problems with Kubernetes and container runtimesĪ Kubernetes cluster using an incompatible container runtime for its version orĬonfiguration could experience these issues cluster-wide: Similar can be applied to any other failing exporter. Here is a configuration example that enables the collector to output debug logs and export them to Splunk Platform or Observability, then you may want to export the collector's logs too. If you already export your logs to Splunk Platform or Splunk The collector's logs are not exported by default. You can change the logging level of the collector from info to debug for troubleshooting. Support bundle scripts are provided to make it easier to collect information:ĭebug logging for the Splunk Otel Collector in Kubernetes kubectl logs my-splunk-otel-collector-k8s-cluster-receiver-7545499bc7-vqdsl > my-splunk-otel-collector-k8s-cluster-receiver.log.kubectl logs my-splunk-otel-collector-agent-fzn4q fluentd > my-splunk-otel-collector-agent-fluentd.log.kubectl logs my-splunk-otel-collector-agent-fzn4q otel-collector > my-splunk-otel-collector-agent.log.Managed or on premises: if managed, which cloud provider and distribution?.Are there any manual customization done to the Kubernetes resources once the.Custom values.yaml file that was applied with helm install command or -set.Which destination is configured: Splunk Platform or Splunk Observability?.In addition, it is important to gather support information including: When opening a support request, it is important to include as much information Gathering Support InformationĮxisting Splunk Observability customers unable to determine why something is notĮnterprise/Cloud customers with Splunk support entitlement can reach out to See Splunk OpenTelemetry Collector troubleshootingĭocumentation. For general troubleshooting of Splunk OpenTelemetry Collector This document covers troubleshooting scenarios specific to KubernetesĮnvironment only.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |