https://signoz.io logo
Join Slack
Powered by
This message was deleted.
# support
s
This message was deleted.
b
Btw, APM feature isn’t working for me in my cluster kernel version is 6.7.1-1-default SUSE Linux distribution
a
You can exclude the pods or namespace in the k8-infra through your values override yaml
b
But it will not help me, I want to exclude ONLY specific logs…
a
to expose signoz frontend, what I did that worked is changing the service port from 3301 to 8080 and change the service type from ClusterIP to LoadBalancer
👍 1
🙌 1
Okay you have tried the k8-infra values right?
b
Not yet, where should I change that? What is k8-infra values?
a
k8s-infra: presets: logsCollection: enabled: true blacklist: enabled: true signozLogs: false namespaces: - kube-systems pods: - hotrod - locust containers: [] additionalExclude: []
b
Hmmm, how should I specify there pattern of logs I want to exclude?
a
You specify the pods that have the logs you want to exclude
b
All logs with this pattern inside body of logs 
kube-probe/1.24
should be excluded from ingest process
a
Wait, it isn't a pod that returns this log?
b
Yes, this is logs of kubernetes probes…(liveness probe), I want to exclude them, it makes a lot of noise and taking a lot of disk space for unnecessary logs
a
yes, i do understand you, but you know the logs is coming from a certain pod, whats the name of the pods that shows the log?
p
All logs with this pattern inside body of logs 
kube-probe/1.24
should be excluded from ingest process
I see what you mean, you want to filter out those specific log lines from all pods, is that correct? It should be possible using Log pipelines as well as adding filter processors in otelcol config in your infra. @Raj Kamal could you please help here?
b
@Prashant Shahi Exactly! What about 2nd issue?
Btw, APM feature isn’t working for me in my cluster
kernel version is 6.7.1-1-default SUSE Linux distribution
p
can you share how you have instrumented your application?
Make sure your otelcollector endpoint IP/domain and port are accurate for the instrumentation.
Also, for external access of SigNoz, you could either opt for LoadBalancer or enable Ingress for frontend.
b
Oh, should it work with otel spans?! If so, nvm everything is works as expected, since I haven’t instrumented my services yet I thought it works with eBPF 😅
p
That can be achieved using OpenTelemetry Operator. Docs - https://signoz.io/docs/tutorial/opentelemetry-operator-usage/
b
Yes, I got it, thanks! now I just need help about how to filter out 
kube-probe/1.24
log lines from all pods, I don’t want to ingest them on SigNoz, it makes a lot of noise, and spending disk space
p
cc @nitya-signoz
n
You can use filter processor to remove logs that you won’t want to be ingested https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/filterprocessor/README.md
b
Thanks! It looks like it’s defined in YAML. Where should this YAML be present within the SigNoz config?
p
you could include that processor in logs pipelines of otelAgent config. Config templating will pick that up and include other components like receivers/exporters.
b
p
correct, you will need to include the processor config there.
b
Great! I got it, I will try that and update you, thanks for your awesome support guys! 🙏 I’m very appreciate it!
It didn’t work, I set it in values yaml, but now, no one log ingested… 😞
p
Did you include it in the 
log
pipeline as well?
b
Here? no..what should I include there?
✅ 1
I succeeded!!!
🙌 4
50 Views
Open in Slack
PreviousNext
Powered by