LIGHT

  • News
  • Docs
  • Community
  • Reddit
  • GitHub

Traceability Id

For each producer request to the sidecar, the sidecar will generate a correlationId and put it into each produce record header for the Kafka message. If users want to use open tracing, then a tracerId will be put into the header. These two values are used per request, and multiple messages share the same correlationId or tracerId.

If an application wants to trace each message produced to Kafka, the traceabilityId can be used in each ProduceRecord. In most cases, the traceabilityId will be picked from the message key or value that can uniquely identify the message.

Here is the source code of ProduceRecord that contains an optional traceabilityId along with key and value. The backend API will populate the value for each record. If any record is missing the traceabilityId, the Kafka message header won’t have this value.

The following is a request with traceabilityId for two of the three records.

curl --location --request POST 'https://localhost:9443/producers/test1' \
--header 'Content-Type: application/json' \
--header 'X-Traceability-Id: common-id' \
--data-raw '{
    "records": [
        {
            "key": "alice",
            "value": {
                "count": 2
            },
            "traceabilityId": "alice-id"
        },
        {
            "key": "john",
            "value": {
                "count": 1
            },
            "traceabilityId": "john-id"
        },
        {
            "key": "alex",
            "value": {
                "count": 2
            }
        }
    ],
    "valueSchemaVersion": 1
   
}'

In the produced Kafka messages, we can see that the alice and john will have the traceabilityId, and alex doesn’t have a traceabilityId.

Here are the headers for alice.

[
  {
    "key": "X-Correlation-Id",
    "stringValue": "rHhqbyUhTkqT7HXWk8qBHg"
  },
  {
    "key": "X-Traceability-Id",
    "stringValue": "alice-id"
  }
]

Here are the headers for john.

[
  {
    "key": "X-Correlation-Id",
    "stringValue": "vw061EzVR6CDB5pgISBL9w"
  },
  {
    "key": "X-Traceability-Id",
    "stringValue": "john-id"
  }
]

Here are the headers for alex.

[
  {
    "key": "X-Correlation-Id",
    "stringValue": "rHhqbyUhTkqT7HXWk8qBHg"
  }
]

You can see the message for alex doesn’t have a traceabilityId because the request record for alex doesn’t have one.

  • About Light
    • Overview
    • Testimonials
    • What is Light
    • Features
    • Principles
    • Benefits
    • Roadmap
    • Community
    • Articles
    • Videos
    • License
    • Why Light Platform
  • Getting Started
    • Get Started Overview
    • Environment
    • Light Codegen Tool
    • Light Rest 4j
    • Light Tram 4j
    • Light Graphql 4j
    • Light Hybrid 4j
    • Light Eventuate 4j
    • Light Oauth2
    • Light Portal Service
    • Light Proxy Server
    • Light Router Server
    • Light Config Server
    • Light Saga 4j
    • Light Session 4j
    • Webserver
    • Websocket
    • Spring Boot Servlet
  • Architecture
    • Architecture Overview
    • API Category
    • API Gateway
    • Architecture Patterns
    • CQRS
    • Eco System
    • Event Sourcing
    • Fail Fast vs Fail Slow
    • Integration Patterns
    • JavaEE declining
    • Key Distribution
    • Microservices Architecture
    • Microservices Monitoring
    • Microservices Security
    • Microservices Traceability
    • Modular Monolith
    • Platform Ecosystem
    • Plugin Architecture
    • Scalability and Performance
    • Serverless
    • Service Collaboration
    • Service Mesh
    • SOA
    • Spring is bloated
    • Stages of API Adoption
    • Transaction Management
    • Microservices Cross-cutting Concerns Options
    • Service Mesh Plus
    • Service Discovery
  • Design
    • Design Overview
    • Design First vs Code First
    • Desgin Pattern
    • Service Evolution
    • Consumer Contract and Consumer Driven Contract
    • Handling Partial Failure
    • Idempotency
    • Server Life Cycle
    • Environment Segregation
    • Database
    • Decomposition Patterns
    • Http2
    • Test Driven
    • Multi-Tenancy
    • Why check token expiration
    • WebServices to Microservices
  • Cross-Cutting Concerns
    • Concerns Overview
  • API Styles
    • Light-4j for absolute performance
    • Style Overview
    • Distributed session on IMDG
    • Hybrid Serverless Modularized Monolithic
    • Kafka - Event Sourcing and CQRS
    • REST - Representational state transfer
    • Web Server with Light
    • Websocket with Light
    • Spring Boot Integration
    • Single Page Application
    • GraphQL - A query language for your API
    • Light IBM MQ
    • Light AWS Lambda
    • Chaos Monkey
  • Infrastructure Services
    • Service Overview
    • Light Proxy
    • Light Mesh
    • Light Router
    • Light Portal
    • Messaging Infrastructure
    • Centralized Logging
    • COVID-19
    • Light OAuth2
    • Metrics and Alerts
    • Config Server
    • Tokenization
    • Light Controller
  • Tool Chain
    • Tool Chain Overview
  • Utility Library
  • Service Consumer
    • Service Consumer
  • Development
    • Development Overview
  • Deployment
    • Deployment Overview
    • Frontend Backend
    • Linux Service
    • Windows Service
    • Install Eventuate on Windows
    • Secure API
    • Client vs light-router
    • Memory Limit
    • Deploy to Kubernetes
  • Benchmark
    • Benchmark Overview
  • Tutorial
    • Tutorial Overview
  • Troubleshooting
    • Troubleshoot
  • FAQ
    • FAQ Overview
  • Milestones
  • Contribute
    • Contribute to Light
    • Development
    • Documentation
    • Example
    • Tutorial
“Traceability Id” was last updated: January 20, 2022: fixes #316 update kafka-sidecar doc to add schema cache and traceability id (d012053)
Improve this page
  • News
  • Docs
  • Community
  • Reddit
  • GitHub
  • About Light
  • Getting Started
  • Architecture
  • Design
  • Cross-Cutting Concerns
  • API Styles
  • Infrastructure Services
  • Tool Chain
  • Utility Library
  • Service Consumer
  • Development
  • Deployment
  • Benchmark
  • Tutorial
  • Troubleshooting
  • FAQ
  • Milestones
  • Contribute