SigNoz Community

Name:             my-release-k8s-infra-otel-agent-psv7k
Namespace:        k8s-infra
Priority:         0
Service Account:  my-release-k8s-infra-otel-agent
Node:             ip-10-200-92-137.il-central-1.compute.internal/10.200.92.137
Start Time:       Sun, 12 Jan 2025 14:32:00 -0500
Labels:           <http://app.kubernetes.io/component=otel-agent|app.kubernetes.io/component=otel-agent>
                  <http://app.kubernetes.io/instance=my-release|app.kubernetes.io/instance=my-release>
                  <http://app.kubernetes.io/name=k8s-infra|app.kubernetes.io/name=k8s-infra>
                  controller-revision-hash=54f56899c4
                  pod-template-generation=1
Annotations:      checksum/config: e36604974160324c46f777a1165d6961b31fec4a868929b286f003df9e974bb6
Status:           Pending
IP:               
IPs:              <none>
Controlled By:    DaemonSet/my-release-k8s-infra-otel-agent
Containers:
  my-release-k8s-infra-otel-agent:
    Container ID:  
    Image:         <http://docker.io/otel/opentelemetry-collector-contrib:0.109.0|docker.io/otel/opentelemetry-collector-contrib:0.109.0>
    Image ID:      
    Ports:         13133/TCP, 8888/TCP, 4317/TCP, 4318/TCP
    Host Ports:    13133/TCP, 8888/TCP, 4317/TCP, 4318/TCP
    Command:
      /otelcol-contrib
    Args:
      --config=/conf/otel-agent-config.yaml
    State:          Waiting
      Reason:       ContainerCreating
    Ready:          False
    Restart Count:  0
    Requests:
      cpu:      100m
      memory:   100Mi
    Liveness:   http-get http://:13133/ delay=10s timeout=5s period=10s #success=1 #failure=6
    Readiness:  http-get http://:13133/ delay=10s timeout=5s period=10s #success=1 #failure=6
    Environment:
      OTEL_EXPORTER_OTLP_ENDPOINT:              my-release-signoz-otel-collector.platform:4317
      OTEL_EXPORTER_OTLP_INSECURE:              true
      OTEL_EXPORTER_OTLP_INSECURE_SKIP_VERIFY:  false
      OTEL_SECRETS_PATH:                        /secrets
      K8S_CLUSTER_NAME:                         kubernetes-ilcentral1-prod-01
      DEPLOYMENT_ENVIRONMENT:                   production
      K8S_NODE_NAME:                             (v1:spec.nodeName)
      K8S_POD_IP:                                (v1:status.podIP)
      K8S_HOST_IP:                               (v1:status.hostIP)
      K8S_POD_NAME:                             my-release-k8s-infra-otel-agent-psv7k (v1:metadata.name)
      K8S_POD_UID:                               (v1:metadata.uid)
      K8S_NAMESPACE:                            k8s-infra (v1:metadata.namespace)
      SIGNOZ_COMPONENT:                         otel-agent
      OTEL_RESOURCE_ATTRIBUTES:                 signoz.component=$(SIGNOZ_COMPONENT),k8s.cluster.name=$(K8S_CLUSTER_NAME),k8s.node.name=$(K8S_NODE_NAME),host.name=$(K8S_NODE_NAME)
    Mounts:
      /conf from otel-agent-config-vol (rw)
      /hostfs from hostfs (ro)
      /var/lib/docker/containers from varlibdockercontainers (ro)
      /var/log from varlog (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-kzbqp (ro)
Conditions:
  Type                        Status
  PodReadyToStartContainers   False 
  Initialized                 True 
  Ready                       False 
  ContainersReady             False 
  PodScheduled                True 
Volumes:
  otel-agent-config-vol:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      my-release-k8s-infra-otel-agent
    Optional:  false
  varlog:
    Type:          HostPath (bare host directory volume)
    Path:          /var/log
    HostPathType:  
  varlibdockercontainers:
    Type:          HostPath (bare host directory volume)
    Path:          /var/lib/docker/containers
    HostPathType:  
  hostfs:
    Type:          HostPath (bare host directory volume)
    Path:          /
    HostPathType:  
  kube-api-access-kzbqp:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 op=Exists
                             <http://node.kubernetes.io/disk-pressure:NoSchedule|node.kubernetes.io/disk-pressure:NoSchedule> op=Exists
                             <http://node.kubernetes.io/memory-pressure:NoSchedule|node.kubernetes.io/memory-pressure:NoSchedule> op=Exists
                             <http://node.kubernetes.io/not-ready:NoExecute|node.kubernetes.io/not-ready:NoExecute> op=Exists
                             <http://node.kubernetes.io/pid-pressure:NoSchedule|node.kubernetes.io/pid-pressure:NoSchedule> op=Exists
                             <http://node.kubernetes.io/unreachable:NoExecute|node.kubernetes.io/unreachable:NoExecute> op=Exists
                             <http://node.kubernetes.io/unschedulable:NoSchedule|node.kubernetes.io/unschedulable:NoSchedule> op=Exists
Events:
  Type     Reason                  Age                  From               Message
  ----     ------                  ----                 ----               -------
  Normal   Scheduled               40m                  default-scheduler  Successfully assigned k8s-infra/my-release-k8s-infra-otel-agent-psv7k to ip-10-200-92-137.il-central-1.compute.internal
  Warning  FailedCreatePodSandBox  40m                  kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "cb27d0d9180127bc9db8a9d20d5d4ebf21c0defffca9c505041cb5b3aa02bbdc": plugin type="vpc-bridge" name="vpc" failed (add): failed to parse Kubernetes args: failed to get pod IP address my-release-k8s-infra-otel-agent-psv7k: error executing k8s connector: error executing connector binary: exit status 1 with execution error: pod my-release-k8s-infra-otel-agent-psv7k does not have label <http://vpc.amazonaws.com/PrivateIPv4Address|vpc.amazonaws.com/PrivateIPv4Address>
  Warning  FailedCreatePodSandBox  40m                  kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "dfd1bf178c0c11672ded8734cb509100c54d11b37e10e5a65b081dad0a9045ea": plugin type="vpc-bridge" name="vpc" failed (add): failed to parse Kubernetes args: failed to get pod IP address my-release-k8s-infra-otel-agent-psv7k: error executing k8s connector: error executing connector binary: exit status 1 with execution error: pod my-release-k8s-infra-otel-agent-psv7k does not have label <http://vpc.amazonaws.com/PrivateIPv4Address|vpc.amazonaws.com/PrivateIPv4Address>

n

1
2
41

Hi devs, I've installed Signoz using helm on a local minikube cluster and deployed a simple instrume...

c

Chris Mankin

8 months ago

Hi devs, I've installed Signoz using helm on a local minikube cluster and deployed a simple instrumented express app to the same cluster. Services and traces form the app are visible in the Signoz UI. The docs say "When you deploy SigNoz to your kubernetes cluster it will automatically start collecting all the pod logs." Is there some additional setup needed to get the logs coming in, as I'm not seeing anything out of the box? Thanks

c

p

c

3
6
41

<@U06017QDYCF> I am following the tutorial to use a collector and send telemetry to SigNoz, but I am...

b

Brandon Fordham

9 months ago

@Chitransh Gupta I am following the tutorial to use a collector and send telemetry to SigNoz, but I am getting some errors with the documentation's example code for the config.yaml. Any suggestions? https://signoz.io/docs/tutorial/opentelemetry-binary-usage-in-virtual-machine/

2024-10-21T16:07:28.300-0400    warn    zapgrpc/zapgrpc.go:195  [core] [Channel #5 SubChannel #6] grpc: addrConn.createTransport failed to connect to {Addr: "ingest.us.signoz.cloud:443", ServerName: "ingest.us.signoz.cloud:443", }. Err: connection error: desc = "error reading server preface: http2: frame too large"  {"grpc_log": true}

b

p