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

connection_string not supported in azuremonitor exporter #29151

Closed
Toudahl opened this issue Nov 13, 2023 · 5 comments
Closed

connection_string not supported in azuremonitor exporter #29151

Toudahl opened this issue Nov 13, 2023 · 5 comments
Labels
bug Something isn't working exporter/azuremonitor needs triage New item requiring triage

Comments

@Toudahl
Copy link

Toudahl commented Nov 13, 2023

Component(s)

exporter/azuremonitor

What happened?

Description

The connection_string setting does not work for azuremonitor

Steps to Reproduce

Create docker-compose from https://opentelemetry.io/docs/collector/installation/#docker-compose

version: "3.9"

services:
  otel-collector:
    image: otel/opentelemetry-collector-contrib:0.88.0
    volumes:
      - ./otel-collector-config.yaml:/etc/otelcol-contrib/config.yaml
    ports:
      - "4317:4317"

Combine information found in the readme for the azuremonitor exporter, found here with the example configuration found here to create a config file like the one see in the config section

In your terminal, write: docker compose up

Expected Result

The collector starts correctly.

Actual Result

The collector prints an error message and shuts down

Collector version

0.88.0

Environment information

Environment

OS: Windows 11
Docker: 24.0.6, build ed223bc

OpenTelemetry Collector configuration

receivers:
  otlp:
    protocols:
      grpc:
      http:
        
exporters:
  azuremonitor:
    connection_string: "InstrumentationKey=00000000-0000-0000-0000-000000000000;IngestionEndpoint=https://ingestion.azuremonitor.com/"

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [azuremonitor]
    metrics:
      receivers: [otlp]
      exporters: [azuremonitor]
    logs:
      receivers: [otlp]
      exporters: [azuremonitor]

Log output

infrastructure-otel-collector-1  | Error: failed to get config: cannot unmarshal the configuration: 1 error(s) decoding:
infrastructure-otel-collector-1  |
infrastructure-otel-collector-1  | * error decoding 'exporters': error reading configuration for "azuremonitor": 1 error(s) decoding:
infrastructure-otel-collector-1  |
infrastructure-otel-collector-1  | * '' has invalid keys: connection_string
infrastructure-otel-collector-1  | 2023/11/13 12:35:54 collector server run finished with error: failed to get config: cannot unmarshal the configuration: 1 error(s) decoding:
infrastructure-otel-collector-1  |
infrastructure-otel-collector-1  | * error decoding 'exporters': error reading configuration for "azuremonitor": 1 error(s) decoding:
infrastructure-otel-collector-1  |
infrastructure-otel-collector-1  | * '' has invalid keys: connection_string
infrastructure-otel-collector-1 exited with code 1

Additional context

No response

@Toudahl Toudahl added bug Something isn't working needs triage New item requiring triage labels Nov 13, 2023
Copy link
Contributor

Pinging code owners:

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

@Toudahl
Copy link
Author

Toudahl commented Nov 13, 2023

Other than the readme describing the use of connection_string, issue #28853 indicates that it should be supported

@crobert-1
Copy link
Member

Hello @Toudahl, thanks for filing! This functionality was introduced last week, but the latest release was v0.88.0 which was 3 weeks ago. This simply means the feature hasn't been included in a release yet.

Please test again once v0.89.0 has been released, feel free to file an issue if it's still not working then!

@Toudahl
Copy link
Author

Toudahl commented Nov 13, 2023

Hello @Toudahl, thanks for filing! This functionality was introduced last week, but the latest release was v0.88.0 which was 3 weeks ago. This simply means the feature hasn't been included in a release yet.

Please test again once v0.89.0 has been released, feel free to file an issue if it's still not working then!

Apologies - I did not pay attention to the timeline.
Thanks for getting back to me.

@crobert-1
Copy link
Member

No worries! I've run into this myself and been confused multiple times 👍

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

No branches or pull requests

2 participants