This message was deleted.

This message was deleted.

Hi all, I cannot find the API key creation section in SigNoz self-hosted (free version). My SigNoz version is v0.54.0. Do I need to update my version? Is there any solution? Thank you all. ps: In organization section there is no API key section.

Hello, can someone please help me? I don’t understand why my current log data only shows for the past week when I set the time range, and not for the last 15 minutes. Also, how can I view metric data in Signoz, which is self-hosted?

Hi Team, we are facing a issue regarding ingress-nginx, it is creating internal load balancer only with private subnets can anyone please help here. followed https://signoz.io/docs/install/kubernetes/aws/ , https://signoz.io/docs/tutorial/setting-up-tls-for-signoz/ below is the override-values.yaml

global:
  storageClass: signoz-gp3
  cloud: aws

clickhouse:
  # layout:
  #   shardsCount: 2
  #   replicasCount: 1
  # zookeeper:
  #   replicaCount: 2
  persistence:
    storageClass: signoz-gp3
    size: 300Gi
  cloudStorage:
    enabled: true
    defaultKeepFreeSpaceBytes: "52428800" # 500MB
    type: s3
    endpoint: <https://ss2-tmp-store/logs-cold-storage/>
    accessKey: <accessKey>
    secretAccess: <secretAccess>
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: dedicated
            operator: In
            values:
            - signoz-c6a.2xlarge
  tolerations:
    - key: "signoz"
      operator: "Equal"
      value: "true"
      effect: "NoExecute"
  

schemaMigrator:
  enableReplication: true


cert-manager:
  enabled: true
  installCRDs: true

  letsencrypt: true
  ingressClassName: nginx
  email: <mailto:john@sentisum.com|john@sentisum.com>

ingress-nginx:
  enabled: true
  controller:
    name: ingress-nginx-controller
    namespace: platform
    service:
      annotations:
        <http://service.beta.kubernetes.io/aws-load-balancer-internal|service.beta.kubernetes.io/aws-load-balancer-internal>: "false"  # Ensure this is set to "false" for external LoadBalancer
      type: LoadBalancer
    ingressClassResource:
      name: nginx
      enabled: true
      default: true

frontend:
  ingress:
    enabled: true
    className: nginx
    hosts:
      - host: <http://signoz.sentisum.com|signoz.sentisum.com>
        paths:
          - path: /
            pathType: ImplementationSpecific
            port: 3301
    tls:
      - secretName: <http://signoz.sentisum.com|signoz.sentisum.com>
        hosts:
          - <http://signoz.sentisum.com|signoz.sentisum.com>
    annotations:
      <http://cert-manager.io/cluster-issuer|cert-manager.io/cluster-issuer>: letsencrypt-prod
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: dedicated
            operator: In
            values:
            - signoz-c6a.2xlarge
  tolerations:
    - key: "signoz"
      operator: "Equal"
      value: "true"
      effect: "NoExecute"


otelCollector:
  replicaCount: 2
  config:
    exporters:
      clickhousetraces:
        timeout: 30s
      clickhouselogsexporter:
        timeout: 30s
    processors:
      batch:
        timeout: 30s
  ingress:
    enabled: true
    className: nginx
    hosts:
      - host: <http://signoz-ingest.sentisum.com|signoz-ingest.sentisum.com>
        paths:
          - path: /
            pathType: ImplementationSpecific
            port: 4317
    tls:
      - secretName: <http://signoz-ingest.sentisum.com|signoz-ingest.sentisum.com>
        hosts:
          - <http://signoz-ingest.sentisum.com|signoz-ingest.sentisum.com>
    annotations:
      <http://cert-manager.io/cluster-issuer|cert-manager.io/cluster-issuer>: letsencrypt-prod
      <http://nginx.ingress.kubernetes.io/ssl-redirect|nginx.ingress.kubernetes.io/ssl-redirect>: "true"
      <http://nginx.ingress.kubernetes.io/backend-protocol|nginx.ingress.kubernetes.io/backend-protocol>: "GRPC"
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: dedicated
            operator: In
            values:
            - signoz-c6a.2xlarge
  tolerations:
    - key: "signoz"
      operator: "Equal"
      value: "true"
      effect: "NoExecute"

Hi Signoz team, I've setup Signoz in a Docker Swarm cluster and configured S3 as per your documentation. I've done this after I already had a lot of data, the Clickhouse folder filled up my disk. It then wrote a lot of data to S3 and removed a significant chunk of data locally. Over the next days and weeks, I noticed two things: 1. Data is being written to S3 👍 2. My local disk is filling up again 👎 So, it seems as if it writes data to S3 but never deletes it from the local disk? What am I missing here?

like a few other folks, I'm having trouble getting a nested json object (

body.message: {...}

) hoisted to attributes. Over time, I might cherry-pick just a few of the attributes but even trying a few techniques (e.g. use JSON parser to temp variable from your JSON Guide) hasn't worked. I was hoping folks here might see the obvious mistake. Details in thread.

This message was deleted.

This message was deleted.

This message was deleted.