AnyValue about opentelemetry-proto HOT 8 CLOSED

ok I have figured that myself
the correct attributes should look like

{
  key: 'myParam',
  value: 'stringValue',
  stringValue: 'foo'
}

so the value needs to point to what has been chosen

from opentelemetry-proto.

ok here are my findings:

1. For json over http this is fine

{
  key: 'myParam',
  value: 'stringValue',
  stringValue: 'foo'
}

2. For grpc or proto over http I cannot force it to work, however I debugged things with serializing proto and such structure is serialising correctly

{
  key: 'myParam',
  value: {
    stringValue: 'foo'
  }
}

Here are my collector files

version: "3"
services:
  # Collector
  collector:
    image: otel/opentelemetry-collector-dev:latest
    command: ["--config=/conf/collector-config.yaml", "--log-level=DEBUG"]
    networks:
      - otelcol
    volumes:
      - ./collector-config.yaml:/conf/collector-config.yaml
    ports:
      - "55680:55680"
    depends_on:
      - zipkin-all-in-one

  # Zipkin
  zipkin-all-in-one:
    image: openzipkin/zipkin:latest
    networks:
      - otelcol
    ports:
      - "9411:9411"

networks:
  otelcol:

receivers:
  otlp:
    protocols:
      grpc:
      http:

exporters:
  zipkin:
    url: "http://zipkin-all-in-one:9411/api/v2/spans"

processors:
  batch:
  queued_retry:

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [zipkin]
      processors: [batch, queued_retry]

From grpc I'm getting error

{
  "code": 13,
  "metadata": {
    "_internal_repr": {},
    "flags": 0
  },
  "details": "grpc: error unmarshalling request: proto: wrong wireType = 2 for field Type"
}

Any suggestions thoughts ?

from opentelemetry-proto.

This should do it:

"attributes":
[
  {
    "key": "host.hostname",
    "value": { "stringValue": "testHost" }
  }
]

We have an automated test that verifies it in the Collector: https://github.com/open-telemetry/opentelemetry-collector/blob/2ba9cdcc2b3c7f45288c1152b97e9ec64b9d6706/receiver/otlpreceiver/otlp_test.go#L80

from opentelemetry-proto.

grpc: error unmarshalling request: proto: wrong wireType = 2 for field Type

This may be an indication that you are using incompatible proto versions. There is no "Type" field in the latest proto version anymore.

from opentelemetry-proto.

@tigrannajaryan have the endpoints url changed maybe then ?

from opentelemetry-proto.

This should do it:

"attributes":
[
  {
    "key": "host.hostname",
    "value": { "stringValue": "testHost" }
  }
]

We have an automated test that verifies it in the Collector: https://github.com/open-telemetry/opentelemetry-collector/blob/2ba9cdcc2b3c7f45288c1152b97e9ec64b9d6706/receiver/otlpreceiver/otlp_test.go#L80

The collector indeed accepts this (only json over http) but there aren't values near tags in zipkin, however this:

{
  key: 'telemetry.sdk.version',
  value: 'stringValue',
  stringValue: '0.9.0'
}

works fine and tags in zipkins are shown

from opentelemetry-proto.

it seems like this might be an issue with collector itself I have tested several different version of latest collector docker and none of them works fine - they all have different problems. I have created a new issue, describing errors for only latest
open-telemetry/opentelemetry-collector#1363

from opentelemetry-proto.

Closing this since the issue in the collector is fized

from opentelemetry-proto.