# Shema Registry not showing in APM Service Map

**URL:** <https://discuss.elastic.co/t/shema-registry-not-showing-in-apm-service-map/360988>\
**Category:** APM\
**Tags:** docker, java\
**Created:** [June 6, 2024, 4:21pm UTC](https://discuss.elastic.co/t/shema-registry-not-showing-in-apm-service-map/360988 "2024-06-06T16:21:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![FranM](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/franm/32/135098_2.png) [@FranM](https://discuss.elastic.co/u/FranM)\
**Post date:** [June 6, 2024, 4:21pm UTC](https://discuss.elastic.co/t/shema-registry-not-showing-in-apm-service-map/360988/1 "2024-06-06T16:21:13Z")

</div>

Hello, I am using a Spring Boot Microservice as kafka producer, and I was wondering why I am not able to see the connections to Schema Registry in Service Map part in kibana APM part.  
I am using  
co.elastic.apm:apm-agent-api:1.50.0  
co.elastic.apm:elastic-apm-agent:1.50.0  
com.microsoft.azure:azure-schemaregistry-kafka-avro:1.1.1

This is what I view from kibana APM:

 ![2024-06-06 18_04_53-Service Map -Services - APM - Observability - Elasti](https://us1.discourse-cdn.com/elastic/original/3X/f/a/fa3090a0524289951e7976bb4b3184efb615eef4.png)

The connection to schema registry is done correctly before sending a message, but still doesn't appear in Service Map nor in the traces.

**Kibana version** : v 8.12.2

**Elasticsearch version** : v 8.12.2

**APM Server version** : v 8.12.2

**APM Agent library version** : v 1.50.0

Thanks for your help

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [June 7, 2024, 7:33am UTC](https://discuss.elastic.co/t/shema-registry-not-showing-in-apm-service-map/360988/2 "2024-06-07T07:33:36Z")

</div>

Hi,

From what I understand `azure-schemaregistry-kafka-avro` is responsible for serialization with the avro format but relies on the apache kafka clients as we can see from the [maven dependencies](https://repo1.maven.org/maven2/com/microsoft/azure/azure-schemaregistry-kafka-avro/1.1.1/azure-schemaregistry-kafka-avro-1.1.1.pom) in the pom:

```auto
<dependency>
  <groupId>org.apache.kafka</groupId>
  <artifactId>kafka-clients</artifactId>
  <version>3.3.1</version>
</dependency>

```

So, if you have only one Kafka client used in your application, then it should use the same and also be instrumented in the same way.

It is still possible that the Kafka instrumentation does not work as expected in this particular case, but I don't see how that would be different from the two other kafka endpoints that are shown in the map.