TLDR sudhanshu faces issues with log collection despite successful application performance monitoring after deploying Signoz on OCI k8s cluster. Prashant suggests updating paths used for log collection and verifying container logs on the nodes. Log files' paths seem correct, but issues persist. Further solutions are needed.
Hi sudhanshu :wave:
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:
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 Any idea in debugging?
<#C01HWQ1R0BC|support>
Is compulsory to deploy signoz in platform namespace Prashant
?
not mandatory, you can deploy in any namespace.
Any other way to debug
> Any idea in debugging? can you try to ssh into the nodes and find the path for container logs?
I tried
it is /var/log/pods/
Path wise ok
I checked
can you share complete path of the container log file?
```/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.
sudhanshu
Wed, 11 Oct 2023 11:56:08 UTCI deployed signoz in oci k8s cluster . APM working fine but logs are not coming . Below is my k8s-infra yaml , ```k8s-infra: # -- Whether to enable K8s infra monitoring enabled: true # -- Endpoint/IP Address of the SigNoz or any other OpenTelemetry backend. # Set it to `` for SigNoz SaaS.
#
# If set to null and the chart is installed as dependency, it will attempt
# to autogenerate the endpoint of SigNoz OtelCollector.
otelCollectorEndpoint: null
# -- Whether the OTLP endpoint is insecure.
# Set this to false, in case of secure OTLP endpoint.
otelInsecure: true
# -- Whether to skip verifying the certificate.
insecureSkipVerify: false
# -- API key of SigNoz SaaS
signozApiKey: ""
# OTLP receivers TLS
otelTlsSecrets:
# -- Whether to enable OpenTelemetry OTLP secrets
enabled: false
# -- Path for the secrets volume
path: /secrets
# -- Name of the existing secret with TLS certificate, key and CA to be used.
# Files in the secret must be named `cert.pem`, `key.pem` and `ca.pem`.
existingSecretName:
# -- TLS certificate to be included in the secret
certificate: |
<INCLUDE_CERTIFICATE_HERE>
# -- TLS private key to be included in the secret
key: |
<INCLUDE_PRIVATE_KEY_HERE>
# -- TLS certificate authority (CA) certificate to be included in the secret
ca: ""
# -- Which namespace to install k8s-infra components.
# By default installed to the namespace same as the chart.
namespace: ""
# -- Presets to easily set up OtelCollector configurations.
presets:
loggingExporter:
enabled: false
# Verbosity of the logging export: basic, normal, detailed
verbosity: basic
# Number of messages initially logged each second
samplingInitial: 2
# Sampling rate after the initial messages are logged
samplingThereafter: 500
logsCollection:
enabled: true
include:
- /var/log/pods/*/*/*.log
startAt: beginning
includeFilePath: true
includeFileName: false
blacklist:
enabled: true
signozLogs: false
namespaces:
- kube-system
pods:
- hotrod
- locust
containers: []
additionalExclude: []```