Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 352. Mapping rules

The service name mapping for server occurs using the following rules

  1. Is there an exclude pattern that matches the endpoint uri of the from endpoint? If yes then skip.
  2. Is there a match in the serviceServiceMapping that matches the endpoint uri of the from endpoint? If yes, then use the found service name
  3. Is there a match in the serviceServiceMapping that matches the route id of the current route? If yes, then use the found service name
  4. Is there a match in the serviceServiceMapping that matches the original route id where the exchange started? If yes, then use the found service name
  5. No service name was found, the exchange is not traced by zipkin

The service name mapping for client occurs using the following rules

  1. Is there an exclude pattern that matches the endpoint uri of the from endpoint? If yes then skip.
  2. Is there a match in the clientServiceMapping that matches the endpoint uri of endpoint where the message is being sent to? If yes, then use the found service name
  3. Is there a match in the clientServiceMapping that matches the route id of the current route? If yes, then use the found service name
  4. Is there a match in the clientServiceMapping that matches the original route id where the exchange started? If yes, then use the found service name
  5. No service name was found, the exchange is not traced by zipkin

352.1. No client or server mappings
Copy link

If there has been no configuration of client or server service mappings, CamelZipkin runs in a fallback mode, and uses endpoint uris as the service name.

In the example above, this would mean the service names would be defined as if you add the following code yourself: 

zipkin.addServerServiceMapping("activemq:queue:inbox", "activemq:queue:inbox");
zipkin.addClientServiceMapping("http:someserver/somepath", "http:someserver/somepath");

This is not a recommended approach, but gets you up and running quickly without doing any service name mappings. However, when you have multiple systems across your infrastructure, then you should consider using human-readable service names, that you map to instead of using the camel endpoint uris.

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top