Hello @Vishal Sharma , we connected some time back. Here is our configuration for self hosted signoz as of now. We followed: https://signoz.io/docs/aws-monitoring/lambda/lambda-traces/#aws-lambda-auto-instrumentation-for-tracing-1 I'm using nodejs, with serverless framework. Env Variables

OTEL_EXPORTER_OTLP_ENDPOINT: ${self:custom.CONFIG.OTEL_EXPORTER_OTLP_ENDPOINT}
    AWS_LAMBDA_EXEC_WRAPPER: /opt/otel-handler
    OTEL_PROPAGATORS: tracecontext
    OTEL_SERVICE_NAME: service-${self:custom.STAGE}
    OTEL_TRACES_SAMPLER: always_on
    OPENTELEMETRY_COLLECTOR_CONFIG_FILE: /var/task/collector.yaml
    OTEL_LAYER_1: arn:aws:lambda:ap-south-1:184161586896:layer:opentelemetry-nodejs-0_11_0:1
    OTEL_LAYER_2: arn:aws:lambda:ap-south-1:184161586896:layer:opentelemetry-collector-amd64-0_12_0:1
    OTEL_EXPORTER_OTLP_ENDPOINT: <https://signoz.secretdomain.com>

Collector.yaml

# collector.yaml
receivers:
  otlp:
    protocols:
      # grpc:
      #   endpoint: 'localhost:4317'
      http:
        endpoint: 'localhost:4318'
 
processors:
  batch: {}
  resource/env:
        attributes:
        - key: deployment.environment
          value: dev # can be dev, prod, staging etc. based on your environment
          action: upsert

exporters:
  otlp:
    endpoint: "<https://signoz.secretdomain.com:4318>"
  # tls:
  #   insecure: false
  debug:
    verbosity: normal

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch, resource/env]
      exporters: [otlp]

Our metrics tab is empty, and data is not that great, we are not seeing any status, response code, referrer etc details, which is crucial for APM. Can you please help us?

Hey @Abhishek Mudgal, can you try with the debug exporter and check if metrics are getting exported?

@Nagesh Bansal

[otlp, debug]

under service.pipelines.traces.exporters ?