Hey folks, I added the "hostmetrics" dashboard, bu...
# support
s
Hey folks, I added the "hostmetrics" dashboard, but I can't see the "hostname" for some reason. Also, I can't see it in "Infra Monitoring". This is the config of my collector container:
Copy code
otel-collector:
    !!merge <<: *db-depend
    image: signoz/signoz-otel-collector:${OTELCOL_TAG:-v0.111.42}
    container_name: signoz-otel-collector
    command:
      - --config=/etc/otel-collector-config.yaml
      - --manager-config=/etc/manager-config.yaml
      - --copy-path=/var/tmp/collector-config.yaml
      - --feature-gates=-pkg.translator.prometheus.NormalizeName
    volumes:
      - ./otel-collector-config.yaml:/etc/otel-collector-config.yaml
      - ../common/signoz/otel-collector-opamp-config.yaml:/etc/manager-config.yaml
    
    environment:
      - OTEL_RESOURCE_ATTRIBUTES=host.name=${OTEL_HOSTNAME:-signoz-host},os.type=linux
      - LOW_CARDINAL_EXCEPTION_GROUPING=false
    ports:
      # - "1777:1777"     # pprof extension
      - "4317:4317" # OTLP gRPC receiver
      - "4318:4318" # OTLP HTTP receiver
    depends_on:
      signoz:
        condition: service_healthy
And this is collector config:
Copy code
hostmetrics:
    collection_interval: 60s  # Frequency of metrics collection.
    scrapers:
      cpu:
        metrics:
          system.cpu.logical.count:
            enabled: true
      load:
        cpu_average: true
      memory: {}
      disk: {}
      filesystem:
        metrics:
          system.filesystem.utilization:
            enabled: true
      network:
        metrics:
          system.memory.limit:
            enabled: true
      process:
        mute_process_name_error: true
        mute_process_exe_error: true
        mute_process_io_error: true
      processes: {}
processors:
  batch:
    send_batch_size: 10000
    send_batch_max_size: 11000
    timeout: 10s
  resourcedetection:
    # Using OTEL_RESOURCE_ATTRIBUTES envvar, env detector adds custom labels.
    detectors: [env, system]
    system:
      hostname_sources: [dns, os]
    timeout: 2s
service:
  telemetry:
    logs:
      encoding: json
    metrics:
      address: 0.0.0.0:8888
  extensions:
    - health_check
    - pprof
  pipelines:
    traces:
      receivers: [otlp]
      processors: [signozspanmetrics/delta, batch]
      exporters: [clickhousetraces]
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [clickhousemetricswrite, signozclickhousemetrics]
    metrics/prometheus:
      receivers: [prometheus, hostmetrics]
      processors: [resourcedetection, batch]
      exporters: [clickhousemetricswrite/prometheus, signozclickhousemetrics]
Do you know what the source of this issue can be? Also, it's a silly question, but does it work when I run Signoz as a standalone Docker deployment?
n
Hey @Sergei Zobov How are you running signoz?