https://signoz.io
Join Slack
This message was deleted.
# general
s
This message was deleted.
a
@Tal Cohen you mean for logs? @Prashant Shahi has been working on it. He can update on release timeline for the same
t
@Ankit Nayan Yes, need exclude to logs in first place, if I will be able to exclude open telemetry for the specific namespace it will be even better. But logs is the most important because the services in this namespace I need to exclude generate huge amount of logs that I don't need in SigNoz
a
yes...that is exactly which @Prashant Shahi is working on
p
Hey @Tal Cohen 👋 We have already updated 
k8s-infra
chart to include presets to blacklist log collection from specific namespace, pods, and containers. We will be updating dependency version in SigNoz chart by EOD.
t
Thanks a lot
p
@Tal Cohen You can track the new additions in this PR: https://github.com/SigNoz/charts/pull/102 Do check out the preset configurations in 
values.yaml
👀 1
@Tal Cohen That PR has been merged. You should be able to use it after upgrading to latest chart. https://signoz.io/docs/operate/kubernetes/#upgrade You should be able to include the following in 
override-values.yaml
and include/excluding log capturing from any custom namespace, pod, or containers.
Copy code
k8s-infra:
  presets:
    logsCollection:
      enabled: true
      blacklist:
        enabled: true
        # This disables log capuring of all pods in SigNoz and k8-infra namespace
        signozLogs: false
        namespaces:
          - kube-system
        pods:
          - hotrod
          - locust
        containers: []
9 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