Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

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
Copier lien

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

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2026 Red HatRetour au début