Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

このコンテンツは選択した言語では利用できません。

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
リンクのコピー

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

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2026 Red Hatトップに戻る