Hi, Team, Awesome work. I am setting up signoz where I don't like to get logs from cretin namespaces. There exists blacklist option, but it is not working. Below is my helm.values and chart.

signoz:
  global:
    clusterName: "my-cluster"
  k8s-infra:
    presets:
      logCollection:
        enabled: true
        blacklist:
          enabled: true
          signozLogs: false
          namespaces:
            - kube-system
            - mongodb-cluster
            - istio-system
            - kube-public
            - kube-node-lease
            - argocd
            - cert-manager
            - ingress-nginx
            - linkerd
            - linkerd-viz
            - external-dns
            - external-secrets
            - platform

  clickhouse:
    persistence:
      enabled: true
      size: 30Gi
  frontend:
    ingress:
      enabled: true
      className: "nginx"
      hosts:
        - host: <http://signoz.xyz.com|signoz.xyz.com>
          paths:
            - path: /
              pathType: ImplementationSpecific
              port: 3301
      tls:
        - secretName: int.xyz.com-tls
          hosts:
            - <http://signoz.xyz.com|signoz.xyz.com>
    nginxExtraConfig: |
      client_max_body_size 24M;
      large_client_header_buffers 8 16k;
  alertmanager:
    name: "alertmanager"
    replicaCount: 1

    service:
      type: ClusterIP
      port: 9093
    ingress:
      enabled: false
    resources:
      requests:
        cpu: 100m
        memory: 100Mi
    persistence:
      enabled: true
      accessModes:
        - ReadWriteOnce
      size: 1000Mi

and Chart.yaml

apiVersion: v2
appVersion: "1.0"
description: A Helm chart for Signoz
name: signoz
version: 0.0.1

dependencies:
  - name: signoz
    alias: signoz
    version: 0.10.2
    repository: <https://charts.signoz.io>

Is there any way to make it work? Thanks for your help and efforts. BR,

@Hassnat so you are also seeing logs from namespaces like kube-system?

@Pranay Yes i do see from all above namespaces, including kube-system

So, one expt. you can try is: if you do

logsCollection:

enabled : false

Does it stop sending logs? https://signoz.io/docs/userguide/collect_kubernetes_pod_logs/#steps-to-disable-automatic-pod-logs-collection

@Pranay No i still see logs, although i re-installed chart

@Prashant Shahi Do you have any insights here on what could be going wrong?

Hi @Hassnat 👋 I see you are using SigNoz chart as dependency to your own. Any particular reason for that?

Hi @Prashant Shahi , i am using argocd gitops. As a minimal application here is the app which is responsible for installing signoz. its a standard way i believe. here is my app defination and above in chat are my Chart, and values.yaml

apiVersion: <http://argoproj.io/v1alpha1|argoproj.io/v1alpha1>
kind: Application
metadata:
  name: signoz
  namespace: argocd
  finalizers:
    - <http://resources-finalizer.argocd.argoproj.io|resources-finalizer.argocd.argoproj.io>
spec:
  destination:
    namespace: platform
    server: <https://kubernetes.default.svc>
  project: monitoring
  source:
    path: kustomizations/cluster-apps/monitoring/signoz/helm
    repoURL: <https://gitlab.com/my-user/argocd/app-of-apps.git>
    targetRevision: main
    helm:
      valueFiles:
        - values.yaml
  syncPolicy:
    automated:
      prune: true
      selfHeal: true

@Hassnat I will be looking to running SigNoz on ArgoCD. Will get back to you.

@Prashant Shahi Good day. Have you had any chance to look into it. Thanks

Hi, I am also interested in gitops style deployment with Argo CD, currently I'm having few issues, not sure if those should be solved on Argo CD side or signoz. Deployed CRDs are instantly OutOfSync, which can be remediated with

ignoreDifferences

. Also Argo CD is trying to prune PV for signoz-clickhouse which I'm not sure how to handle as I'm not that familiar with CRDs where it is coming from. @Hassnat @Prashant Shahi sorry for pinging, but this seems like an old thread with little chance of resurrection without notification.

@A Nav Back then, I tested it. SIgNoz is usable without any issue but ArgoCD say that clickhosue is out of sync. It is an issue with clickhouse-operator that is used by SigNoz. Related issue: https://github.com/Altinity/clickhouse-operator/issues/1137

Thanks, seems the OutOfSync CRDs are already fixed in unreleased version as per latest comment on that issue. However there is another issue with PV: https://github.com/SigNoz/charts/issues/86

@A Nav Thanks for pointing that out. I was able to use SigNoz with ArgoCD, however OutOfSync issue in ClickHouse operator CRD and pvc was still there.

The CRD issue should "resolve itself" with the release of clickhouse-operator 0.21. For the PV problem I'm afraid I have no helm templating experience to make that PR in a time efficient manner.