awscloudwatch: profile: 'default' region: ...
# support
a
awscloudwatch: profile: 'default' region: us-east-1 logs: poll_interval: 5m groups: named: cw-loggroup-1:
n
@Prashant Shahi he mentioned that he is able to describe log group and log streams from the instace where it is running the collector, do you think any other access might be required ? Also @Anil do you notice something in the otel collector logs about the cloudwatch receiver ?
a
I don’t see any logs related to cloud watch receiver
n
did you add the receiver in the logs pipelines of your config ?
a
Yes I did
Hello @Prashant Shahi @nitya-signoz please do needful. I am not able to see any errors in the logs related to cloudwatch receiver to debug further. it simply stuck at prometheus metrics step.
Please share me the sample config.yaml file for cloud watch receiver
n
When I was testing, this is the IAM that I used
Copy code
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "VisualEditor0",
      "Effect": "Allow",
      "Action": [
        "logs:DescribeLogGroups",
        "logs:FilterLogEvents"
      ],
      "Resource": "arn:aws:logs:*:090340947446:log-group:*"
    }
  ]
}
receiver :-
Copy code
awscloudwatch:
    region: us-east-1
    logs:
      poll_interval: 1m
      groups:
        autodiscover:
          limit: 100
          prefix: application
a
In my case I have log:* for all log groups
I am using the same config but not sure why it is not even showing errors in logs in case of any permission error
Can we connect in huddle for quick review
Please
Let me know
n
Before that can you restart the collector and check the logs, it should say something about starting the cloudwatch receiver
a
I have restarted multiple times but no clue on cloud watch receiver
n
ok can do a short huddle
a
Great
Let me call you in huddle in 2 min
Sorry
Let me call you
n
ok
It was a bug in otel upstream https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/32345 • solved by adding prefix