https://signoz.io logo
#support
Title
# support
j

Juha Patrikainen

03/20/2023, 1:48 PM
Hello! I would be glad if someone could assist me. We have installed SigNoz Helm chart (0.12.1) and also k8s-infra chart as well. K8s-infra chart is with default values (Oracle OKE 1.23.4). Problem is that kubernetes pod logs are not visible in SigNoz. In otel agent logs I can see that it detects the file to watch in node:
2023-03-20T11:57:39.619Z    info    fileconsumer/file.go:171    Started watching file   {"kind": "receiver", "name": "filelog/k8s", "pipeline": "logs", "component": "fileconsumer", "path": "/var/log/pods/*********/configuration/0.log"}
I have verified that file contains all the logs for the container. There are no errors visible in agent logs, signoz-otel-collector logs or clickhouse logs, but the logs are not visible in SigNoz.
signoz-k8s-infra-otel-agent-nz7rk.log
signoz-otel-collector-678d7d95f9-j45f5.log
n

nitya-signoz

03/20/2023, 3:21 PM
There is some issue with the Oracle cloud which stops the otel collector from reading the logs compared to other service providers like AWS. We haven’t prioritized it yet. Can you check if you can manually access the log files from the otel collector pod in the path `/var/log/pods/`**`
j

Juha Patrikainen

03/20/2023, 3:50 PM
@nitya-signoz You mean from otel agent? Can not exec into container 🙁
kubectl exec -i -t -n platform signoz-k8s-infra-otel-agent-nz7rk -c signoz-k8s-infra-otel-agent -- sh -c "clear; (bash || ash || sh)"
ERRO[0000] exec failed: unable to start container process: exec: "sh": executable file not found in $PATH
command terminated with exit code 255
@nitya-signoz Is there already issue on this? This is hurting us because we use OCI.
n

nitya-signoz

03/22/2023, 4:10 AM
Hey can you please create an issue on this ?
j

Juha Patrikainen

04/05/2023, 5:11 PM
2 Views