Hello everyone I m going to deploy SigNoz on AWS EKS using t

Question

Hello everyone I m going to deploy SigNoz on AWS EKS using the helm chart In our cluster there are few namespaces and I need the ability not to monitor some of them or to specify which namespace to monitor Is there a way to do that

Ankit Nayan · Answer

< Tal Cohen> you mean for logs < Prashant Shahi> has been working on it He can update on release timeline for the same

Tal Cohen · Answer

< 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

Ankit Nayan · Answer

yes that is exactly which < Prashant Shahi> is working on

Prashant Shahi · Answer

Hey < Tal Cohen> wave 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

Tal Cohen · Answer

Thanks a lot

Prashant Shahi · Answer

< Tal Cohen> You can track the new additions in this PR Do check out the preset configurations in `values yaml`

Prashant Shahi · Answer

< Tal Cohen> That PR has been merged You should be able to use it after upgrading to latest chart You should be able to include the following in `override values yaml` and include excluding log capturing from any custom namespace pod or containers ```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 ```