Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
backbone-message-format backbone-message-format
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Communications Backbone System
  • backbone-message-formatbackbone-message-format
  • Issues
  • #96

Closed
Open
Created Feb 14, 2025 by Trishna Saeharaseelan@trishnaOwner

Add "route"/"hops" optional field to header

To show the client_ids of relays (if there are any) between actual source Comms Backbone and actual destination of Comms Backbone

  "header": {
    "message_ID": "09547d73-b8de-49cf-afa4-911852d7a246",
    "timestamp": "2025-02-14T13:06:14.430488Z",
    "version": 2,
    "source": "nmf-ships",
    "destination": "internal.nmf.ship.rrs-james-cook.from_platform.platform_status",
    "delivery_type": "publish",
    "route": ["proj-x-relay", "internal-relay"],  // optional field denoting client_ids of adapters, like relay adapters, passing this message
    "encoded": false
  }
Edited Feb 14, 2025 by Trishna Saeharaseelan
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking