# Apm tracing has some trouble from dapr

**URL:** <https://discuss.elastic.co/t/apm-tracing-has-some-trouble-from-dapr/309636>\
**Category:** APM\
**Tags:** open-telemetry\
**Created:** [July 14, 2022, 11:15am UTC](https://discuss.elastic.co/t/apm-tracing-has-some-trouble-from-dapr/309636 "2022-07-14T11:15:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![LazyZeng](https://avatars.discourse-cdn.com/v4/letter/l/e5b9ba/32.png) [@LazyZeng](https://discuss.elastic.co/u/LazyZeng)\
**Post date:** [July 14, 2022, 11:15am UTC](https://discuss.elastic.co/t/apm-tracing-has-some-trouble-from-dapr/309636/1 "2022-07-14T11:15:44Z")

</div>

APM Server : 7.16.3  
Elastic : 8.1.2  
Dapr : 1.7.1  
Otlp collector: 0.5

I used APM server to save Opentelemetry tracing data, used Otlp expoter and saved data to APM and zipkin. But I has found a problem:  
This is zipkin's tracing datas:

 ![1657796873260](https://us1.discourse-cdn.com/elastic/original/3X/4/6/4600ffd8d3f4af93e505c518c7f95e9eb736a7b6.png)

next is APM tracing data:

 ![1657796978472](https://us1.discourse-cdn.com/elastic/original/3X/1/e/1e0ebacd98e195ac188bc52a31f2369ffa4b02f7.png)

The result is APM's data less one, which is called by `dapr invoke --app-id appid --method methodName` , runing mode is sidecar with grpc , the tracing data is

```auto
{
    "traceId": "f82f08ce1349a4d998f14de04476f539",
    "id": "c43c4e11289f176e",
    "kind": "CLIENT",
    "name": "calllocal/test-server/amazing",
    "timestamp": 1657791087536411,
    "duration": 89351,
    "localEndpoint": {
      "serviceName": "test-server",
      "ipv4": "192.168.4.114"
    },
    "tags": {
      "dapr.api": "POST /v1.0/invoke/test-server/method/Amazing",
      "dapr.protocol": "http",
      "dapr.status_code": "200",
      "net.peer.name": "test-server",
      "opencensus.status_description": "OK",
      "rpc.service": "ServiceInvocation"
    }
  }

```

Is APM suported dapr with grpc ?

---

<div class="post-metadata">

**Author:** ![LazyZeng](https://avatars.discourse-cdn.com/v4/letter/l/e5b9ba/32.png) [@LazyZeng](https://discuss.elastic.co/u/LazyZeng)\
**Post date:** [July 14, 2022, 11:18am UTC](https://discuss.elastic.co/t/apm-tracing-has-some-trouble-from-dapr/309636/2 "2022-07-14T11:18:16Z")

</div>

```auto
 otlp/elastic:
    endpoint: "0.0.0.0:1820"  

...

traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [zipkin,otlp/elastic,file]

```

This is otlp config.yaml.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 4, 2022, 7:19am UTC](https://discuss.elastic.co/t/apm-tracing-has-some-trouble-from-dapr/309636/3 "2022-08-04T07:19:05Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.