Skip to content
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

Open
thilee-siva opened this issue Sep 29, 2024 · 2 comments
Open
Labels
bug Something isn't working needs triage New item requiring triage receiver/awscloudwatch Stale

Comments

@thilee-siva
Copy link

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

receivers:
  awscloudwatch:
    profile: "${PROFILE}"
    region: "${REGION}"
    logs:
      poll_interval: 1m
      groups:
        autodiscover:
          limit: 100

Log output

N/A

Additional context

N/A

@thilee-siva thilee-siva added bug Something isn't working needs triage New item requiring triage labels Sep 29, 2024
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

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 @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage New item requiring triage receiver/awscloudwatch Stale
Projects
None yet
Development

No branches or pull requests

1 participant