OpenTelemetry Contrib using Mongodbatlasreceiver prompts "server busy"

[ashishstationcasinos]

Component(s)

receiver/mongodbatlas

What happened?

Description

Deployed OpenTelemetry- contrib on the kubernetes Cluster below is the yaml file

apiVersion: v1
kind: Namespace
metadata:
  name: dev-otelcol
---
apiVersion: opentelemetry.io/v1alpha1
kind: OpenTelemetryCollector
metadata:
  name: dev-otelcol
  namespace: dev-otelcol
spec:
  config: |
    receivers:
      mongodbatlas:
         public_key: xxxxx
         private_key: xxxxxxxxxxxxx
    exporters:
      debug:
        verbosity: detailed
    service:
     telemetry:
       logs:
         level: DEBUG
     pipelines:
        metrics:
          receivers: [mongodbatlas]
          exporters: [debug]

Steps to Reproduce

Deployed opentelemetry Operator with Helm chart with collection image otel/opentelemetry-collector-contrib-0.99.0 and Deployed OpenTelemetry Collector with Above Config

Expected Result

It should collect the metrics from mongoDB Atlas (AWS cloud)

Actual Result

2024-05-14T01:51:45.996Z        warn    internal/mongodb_atlas_client.go:98     server busy, retrying request   {"kind": "receiver", "name": "mongodbatlas", "data_type": "metrics", "attempts": 1, "delay": 4.519836244}
2024-05-14T01:51:50.712Z        warn    internal/mongodb_atlas_client.go:98     server busy, retrying request   {"kind": "receiver", "name": "mongodbatlas", "data_type": "metrics", "attempts": 2, "delay": 9.24399017}
2024-05-14T01:52:23.989Z        warn    internal/mongodb_atlas_client.go:98     server busy, retrying request   {"kind": "receiver", "name": "mongodbatlas", "data_type": "metrics", "attempts": 1, "delay": 5.914400691}
2024-05-14T01:52:30.098Z        warn    internal/mongodb_atlas_client.go:98     server busy, retrying request   {"kind": "receiver", "name": "mongodbatlas", "data_type": "metrics", "attempts": 2, "delay": 10.287168144}
2024-05-14T01:52:40.638Z        warn    internal/mongodb_atlas_client.go:98     server busy, retrying request   {"kind": "receiver", "name": "mongodbatlas", "data_type": "metrics", "attempts": 3, "delay": 14.997058522}

Collector version

0.99.0

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

receivers:
      mongodbatlas:
         public_key: xxxxx
         private_key: xxxxxxxxxxxxx
    exporters:
      debug:
        verbosity: detailed
    service:
     telemetry:
       logs:
         level: DEBUG
     pipelines:
        metrics:
          receivers: [mongodbatlas]
          exporters: [debug]

Log output

No response

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/mongodbatlas: @djaglowski @schmikei

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

[ashishstationcasinos]

any update on this ?

[github-actions]

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:

• receiver/mongodbatlas: @djaglowski @schmikei

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