https://signoz.io
Join Slack
This message was deleted.
# support
s
This message was deleted.
p
Hi @sudhanshu dev 👋 OCI does not use docker as CRI hence the issue with log collection. It uses CRI-O.
log_dir="/var/log/crio/pods" The default log directory where all logs will go unless directly specified by the kubelet.
Ref: https://github.com/cri-o/cri-o/blob/main/docs/crio.conf.5.md#crio-table Can you try using that crio logs path in the include configuration of log collection instead of docker path? override-values.yaml
Copy code
k8s-infra:
  presets:
    logsCollection:
      enabled: true
      include:
        - /var/log/crio/pods/*/*/*.log
PS: Log collection blacklist will only work via 
additionalExclude
and not others.
s
Tried but still did not work. I even tried with path /var/log/containers/*.log
if fluentbit and otelcollector running on the same machine and tailing the same path. Does it create any issue?
I tried to send logs using python sdk to otel collector and it is working fine means issues most likely to logs path or k8s logging config
@Prashant Shahi Any idea in debugging?
#C01HWQ1R0BC
Is compulsory to deploy signoz in platform namespace @Prashant Shahi
?
p
not mandatory, you can deploy in any namespace.
s
Any other way to debug
p
Any idea in debugging?
can you try to ssh into the nodes and find the path for container logs?
s
I tried
it is /var/log/pods/
Path wise ok
I checked
p
can you share complete path of the container log file?
s
Copy code
/var/log/pods/poc-dev_game-centre-9c6668c99-rrksr_b65c2fe1-d866-42ed-9251-2400eef9a13f/game-centre/559.log
/var/log/pods/default_game-centre-77c96bc74-4vwsj_210c748d-8b69-462d-acc6-fd8cbdced8aa/game-centre/0.log
like these two pods path
I used signoz multiple times for logging. It is first time when I am facing this
APM and monitoring working as expected.
11 Views
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by