Hi, is anyone using SigNoz for EKS clusters? Need some help with that.

I think you should give specific problem so that contributors can help. I'm an SigNoz user and deployed SigNoz for EKS.

Hi @Dang Huy Nguyen, thanks for the response. Actually, I need to transfer my k8s pod logs to Signoz, and I have installed the

helm install my-release signoz/k8s-infra -f override-values.yaml

chart and my pods are running as a daemon set, but I am not sure what the next step is to transfer those logs to the SigNoz dashboard.

Did you give the correct otelexporter endpoint to the signoz otel collector deployed as a part of signoz/signoz chart ?

Yes actually logs are visible now but it is reading only some of mu deployments not all.

@Vinay Mann I faced 2 reasons in the past: 1. Otel Agent is not running on your computing resources. For example, you are using Fargate, k8s-infra does not run on Fargate -> no log. 2. Bug in log ingestion pipeline. For example, I use Vector, and the exporter log format may wrong. Make sure you follow Otel protocol and official document.

Hi @Dang Huy Nguyen @Raghav Awasthi, thanks for the reply. Also i need a little assistance I have set up the tracing using K8S for my Node.js application. Everything is working, but the last step in my Node.js deployment is not working as it is not able to push the image, so do I need any specific credentials for that? ISSUE: "Failed to pull image "nodejs-app:latest": failed to pull and unpack image "docker.io/library/nodejs-app:latest": failed to resolve reference "docker.io/library/nodejs-app:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed"