https://signoz.io logo
Join SlackCommunities
Powered by
but I think it is not running. How can I verify if...
# support
a
but I think it is not running. How can I verify if it is working? where can I see logs for this awscloudwatch receiver
p
you could create a new pipeline with cloudwatch receiver and logging exporter to verify if the data collection part is working
a
what do you mean?
p
It logs information about the incoming data to the console.
a
I was able to see more logs using this config
Copy code
service:
  telemetry:
    logs:
      level: debug
p
That works as well. That is another way to get detailed logs. However, that is applied throughout and not specific to a pipeline.
a
if I remove telemetry.logs.level: debug, how can I make the "debug" exporter to work? I already have it, but it does not show anything in the logs file
Copy code
exporters:
  otlp:
    endpoint: "BANANA:4317"
    tls:
      insecure: true
  debug:
    # verbosity of the logging export: detailed, normal, basic
    verbosity: detailed
service:
  telemetry:
    logs:
      level: debug
    metrics:
      address: 0.0.0.0:8888
  extensions: [health_check, zpages]
  pipelines:
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp]
    metrics/internal:
      receivers: [prometheus, hostmetrics]
      processors: [resourcedetection, batch]
      exporters: [otlp]
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp]
    logs:
      receivers: [otlp, awscloudwatch]
      processors: [batch]
      exporters: [otlp, debug]
p
debug exporter config looks good to me. If it does not show anything in logs, that could mean no incoming logs data either from otlp/awsclouswatch receivers. To be more certain, you can create separate log pipeline like 
logs/aws
with only awscloudwatch receiver and rest of the processors and debug exporter.
a
Copy code
exporters:
  otlp:
    endpoint: "BANANA:4317"
    tls:
      insecure: true
  debug:
    # verbosity of the logging export: detailed, normal, basic
    verbosity: detailed
service:
  telemetry:
    metrics:
      address: 0.0.0.0:8888
  extensions: [health_check, zpages]
  pipelines:
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp]
    metrics/internal:
      receivers: [prometheus, hostmetrics]
      processors: [resourcedetection, batch]
      exporters: [otlp]
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp]
    logs:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp]
    logs/aws:
      receivers: [awscloudwatch]
      processors: [batch]
      exporters: [debug]
Like this one, right?
I removed telemetry.logs.level: debug, and created a new 
logs/aws
pipeline
so now I should see detailed debug logs
did not work. I see no debug logs with this config
18 Views
Open in Slack
PreviousNext
Powered by