-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"limit" in receiver/awscloudwatchreceiver is not functioning as expected #35486
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
receiver/awscloudwatch
What happened?
Description
Steps to Reproduce
I’m using the OpenTelemetry Collector with the awscloudwatch receiver to fetch logs from CloudWatch and send them to Datadog. However, I’ve noticed that the receiver isn’t able to access all the log groups in the region, even though I’ve overridden the default limit of 50.
Expected Result
I have 75 log groups. When writing to any log group that appears alphabetically after the 50th position, I expect the logs to be read by OTEL.
Actual Result
However, it only reads the log groups that are before the 50th position.
Collector version
0.99.0
Environment information
Environment
OS: Ubuntu 20.04
OpenTelemetry Collector configuration
Log output
Additional context
N/A
The text was updated successfully, but these errors were encountered: