https://signoz.io logo
Join Slack
Powered by
Hello everyone, quick question guys, we are giving...
# signoz-cloud
j
Hello everyone, quick question guys, we are giving a try to signoz-cloud and we are currently in the trial period. Currently under the logs/ deployment name and namespace names seems to be empty, but I'm able to get the list of pods and cluster names. I have been trying few options in our values files without lucky, do you have any idea?
v
Hey @Jose Alejandro Dobla , please refer to this document here - https://signoz.io/docs/logs-management/features/logs-quick-filters/#k8s-deployment-name
let us know if you face any issues with the same
j
Hey @Vikrant Gupta thanks for sharing! should I add this filter into the configmap for otel deployment?
I have these attributes into the agent infra-otel-agent
Copy code
k8sattributes:
    extract:
      annotations: []
      labels:
      - from: pod
        key: app
        tag_name: app
      - from: pod
        key: env
        tag_name: env
      - from: node
        key: node.tenancy
        tag_name: node.tenancy
      metadata:
      - k8s.namespace.name
      - k8s.deployment.name
      - k8s.statefulset.name
      - k8s.daemonset.name
      - k8s.cronjob.name
      - k8s.job.name
      - k8s.node.name
      - k8s.node.uid
      - k8s.pod.name
      - k8s.pod.uid
      - k8s.pod.start_time
into the query builder I'm able to filter :
v
Are you getting suggestions for the same in the query builder ? and on filtering above the logs detail view showing the namespace name ?
j
uhmm not it isn't loading as suggestion
image.png
image.png
v
yes the resource attributes are not getting exported correctly, @Vibhu Pandey @nitya-signoz can you please help here ?
j
about namespaces, after running the query and writing manually it started to appear the suggestions of namespaces, but sidebar filter are still empty
also, it only works with that second option
"string" "tag"
"string" "resource" doesn't suggest anything
n
can you share one of your log lines, from the json view of detail page. Also did you do any other custom configuration in the agents, if yes can you share the override file ? Also which k8s platform you are using like EKS/GCP etc ?
Also seems like you might have applied some new changes to your agent because of which even pod name is missing in new logs.
j
hey @nitya-signoz thanks a lot for your time, let me share with you our configuration file
it is running on eks
Copy code
global:
  cloud: aws
  clusterName: ${clusterName}
  deploymentEnvironment: main
otelCollectorEndpoint: ingest.eu.signoz.cloud:443
otelInsecure: false
signozApiKey: ${apikey}
presets:
  kubernetesAttributes:
    enabled: true
    extractMetadatas:
      - k8s.namespace.name
      - k8s.deployment.name
      - k8s.statefulset.name
      - k8s.daemonset.name
      - k8s.cronjob.name
      - k8s.job.name
      - k8s.node.name
      - k8s.node.uid
      - k8s.pod.name
      - k8s.pod.uid
      - k8s.pod.start_time
    extractLabels:
      - tag_name: app
        key: app
        from: pod
      - tag_name: env
        key: env
        from: pod
      - tag_name: node.tenancy
        key: node.tenancy
        from: node
  otlpExporter:
    enabled: true
  loggingExporter:
    enabled: true
  logsCollection:
    # whether to enable log collection
    enabled: true
    whitelist:
      # whether to enable whitelisting
      enabled: true
      # whether to include signoz logs
      signozLogs: false
      # which namespaces to include
      namespaces:
        - realitymax-prod
        - digitalink-prod
        - 3dviewermax-prod
        - nginx2
        - nginx
      # which pods to include
      # which containers to include
      containers: []
      # additional include rules
      additionalInclude: []
    blacklist:
      # whether to enable blacklisting
      enabled: true
      # which namespaces to exclude
      namespaces: []
      # which pods to exclude
      pods:
        - rabbitmq-1
        - rabbitmq-0
      # which containers to exclude
      containers:
        - rabbitmq
      # additional exclude rules
      additionalExclude: []
    operators:
      - type: filter
        expr: 'body matches "GET /health/run HTTP/1.1\" 200"'
        drop_ratio: 1.0
      - type: filter
        expr: 'body matches "POST /api/token/refresh HTTP/1.1\" 200"'
        drop_ratio: 1.0
      - type: filter
        expr: 'body matches "POST /api/pinpoints HTTP/2.0\" 200"'
        drop_ratio: 1.0
      - type: filter
        expr: 'body matches "accepting AMQP connection"'
        drop_ratio: 1.0
      - type: filter
        expr: 'body matches "closing AMQP connection"'
        drop_ratio: 1.0
5 Views
Open in Slack
PreviousNext
Powered by