-
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
* error decoding 'exporters': unknown type: "datadog" for id: "datadog" (valid values: [file kafka prometheus prometheusremotewrite logging otlp otlphttp debug opencensus zipkin]) #30791
Comments
Hello @zendesk-shweta, it looks like when creating your docker image only a subset of exporters are being included in the image. Can you share how you're creating your docker image from the downloaded tar file? Is there a reason why you're creating your own instead of using the published image? |
This is my docker file. We need to do some customisation so we are trying to build image from binary. Kindly suggest what is missing in my docker file while creating the image. WORKDIR /app |
Thanks for sharing your dockerfile! It looks like the problem is this:
This is actually downloading the |
…tch core and contrib (#30832) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> While investigating #30791 I noticed some components are included in releases but their `metadata.yaml` files don't actually include the distribution their included in. These updates should mean metadata is now up to date with what's included in the [core](https://github.com/open-telemetry/opentelemetry-collector-releases/blob/main/distributions/otelcol/manifest.yaml) and [contrib](https://github.com/open-telemetry/opentelemetry-collector-releases/blob/main/distributions/otelcol-contrib/manifest.yaml) releases.
…tch core and contrib (open-telemetry#30832) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> While investigating open-telemetry#30791 I noticed some components are included in releases but their `metadata.yaml` files don't actually include the distribution their included in. These updates should mean metadata is now up to date with what's included in the [core](https://github.com/open-telemetry/opentelemetry-collector-releases/blob/main/distributions/otelcol/manifest.yaml) and [contrib](https://github.com/open-telemetry/opentelemetry-collector-releases/blob/main/distributions/otelcol-contrib/manifest.yaml) releases.
Component(s)
No response
Describe the issue you're reporting
I am using this binary otelcol-contrib_0.93.0_darwin_amd64.tar.gz to create docker image of otel collector. Image is built and pushe dto ECR successfully , however it gives this error " * error decoding 'exporters': unknown type: "datadog" for id: "datadog" (valid values: [file kafka prometheus prometheusremotewrite logging otlp otlphttp debug opencensus zipkin])" when i tried to add datadog as exporter in config file. Below is my datadog file , not sure what i am missing on :
extensions:
memory_ballast:
size_mib: 128
zpages:
endpoint: localhost:55679
receivers:
otlp:
protocols:
grpc:
endpoint: localhost:4317
http:
endpoint: localhost:4318
processors:
batch:
memory_limiter:
# 75% of maximum memory up to 2G
limit_mib: 256
# 25% of limit up to 2G
spike_limit_mib: 200
check_interval: 5s
exporters:
debug:
verbosity: detailed
datadog:
api:
key: " "
service:
pipelines:
traces:
receivers: [otlp]
processors: [memory_limiter, batch]
exporters: [debug, datadog]
metrics:
receivers: [otlp]
processors: [memory_limiter, batch]
exporters: [debug, datadog]
logs:
receivers: [otlp]
processors: [memory_limiter, batch]
exporters: [debug, datadog]
extensions: [memory_ballast, zpages]
The text was updated successfully, but these errors were encountered: