Hi <#C01HWQ1R0BC|> After upgrading to SigNoz v0.90...
# support
t
Hi #C01HWQ1R0BC After upgrading to SigNoz v0.90.1, we're no longer seeing Kubernetes metadata like
k8s.pod.name
and
k8s.pod.ip
in our trace data. Could you please guide us on: • How to re-enable pod-level metadata in traces? • Whether any changes to the OpenTelemetry Collector config (like the
k8sattributes
processor) are needed?
m
We also have this issue - did you manage to resolve this? This is breaking everything.
@Vibhu Pandey this guy also has the issue btw
v
@Nagesh Bansal please check once.
n
Hey @Talari Dhanunjaya Could you please check whether the DOT_METRICS_ENABLED env is set to true in signoz statefulset
Copy code
kubectl get sts/signoz -o yaml
t
@Nagesh Bansal I have installed the with helm chart and cross checked now. - name: DOT_METRICS_ENABLED value: "true" it is already enabled but not getting metadata?
@Matti is it resolved for you? I'm still seeing the issue.
m
It does work for me now, there was/is an issue with specifying
additionalEnvs
key. The new recommended way of adding env vars should be with the
env
key.
t
@Matti can you provide screenshot of it how you added ?
@Nagesh Bansal @Vibhu Pandey could you help me to resolve this ??? iam still facing this issue.
n
Hey @Talari Dhanunjaya, It's not a problem with the DOT Metrics Migration - you need to look for adding resource attributes You can install k8s-infra, which would enrich the trace data with these resource attributes
t
@Nagesh Bansal @Vibhu Pandey I tried installing
k8s-infra
with the below configuration, but I’m still not seeing the Kubernetes resource attributes in my trace data. please find k8s chart values.yaml file below and suggest if any presets: kubernetesAttributes: enabled: true passthrough: false extractMetadatas: - k8s.namespace.name - k8s.deployment.name - k8s.statefulset.name - k8s.daemonset.name - k8s.cronjob.name - k8s.job.name - k8s.node.name - k8s.node.uid - k8s.pod.name - k8s.pod.uid - k8s.pod.start_time - k8s.pod.ip podAssociation: - sources: - from: resource_attribute name: k8s.pod.ip - sources: - from: resource_attribute name: k8s.pod.uid - sources: - from: connection otlpExporter: enabled: true hostMetrics: enabled: false kubeletMetrics: enabled: false clusterMetrics: enabled: false logsCollection: enabled: false k8sEvents: enabled: false resourceDetection: enabled: true timeout: 2s override: false envResourceAttributes: "" config: service: pipelines: traces: receivers: [otlp] processors: [k8sattributes, batch] exporters: [otlp] otelAgent: enabled: true nodeSelector: project: myapplication additionalEnvs: OTEL_EXPORTER_OTLP_ENDPOINT: http://signoz-otel-collector.platform.svc.cluster.local:4318 tolerations: - key: "app" operator: "Equal" value: "myapplication" effect: "NoSchedule" otelDeployment: enabled: false
@Nagesh Bansal @Vibhu Pandey can you please look into this ?
@Nagesh Bansal @Vibhu Pandey cloud you please help with this ??/