Interesting discussion
Not sure we have direct answer for this. However when we developed the precursor to ODA Component and OPEN API in something called Digital Platform reference Architecture
IG1157 Digital Platform Reference Architecture Concepts and Principles v8.0.0
nIput From BT stated an need to have a transaction id that persisted as an operation flow proceeded for say fulfillment.
I'm not sure this got captured in either the APIs or our ODA component specifications.
My tactical suggestion wuld be to polymorphically extend the API with a transaction Id
I wonder if this should be raised as a JIRA change request on the OPEN APIs. However, don't think this will be a quick fix. The slight challenge is one need and need to end view not a per API view. and it gets complicated when say for example a product order gets broken down into individual service and resource. What would be needed is few samples of process flow across component/ APIs to show what gets transferred and how the transaction Id are related /propagated
In the ODA Ecosystems Team we are starting to realize that there are quite a few instrumentation requirements on the flows and API operations to support partnering business models. If you have any example flows and Transaction ID that you can share, we could discuss on the ODA Ecosystems team after our Digital Transformation World even next week. This might help us formulated the requirements to go in the JIRA request(s).
------------------------------
Dave Milham
TM Forum, Chief Architect
------------------------------
Original Message:
Sent: Sep 13, 2022 15:38
From: Ali Rıza Arslan
Subject: Trace ID, Request ID
Earlier our architect group published some information like "don't use header for passing data ". And now I realise that they mean something important, not the requestId etc.
Thanks for the fast response.
Original Message:
Sent: 9/13/2022 2:35:00 PM
From: Derrick Evans
Subject: RE: Trace ID, Request ID
I guess it depends if all you calls downstream are REST style calls over http. If so you can just use a tracking header property?
Original Message:
Sent: 9/13/2022 8:26:00 AM
From: Ali Rıza Arslan
Subject: Trace ID, Request ID
Hi;
Our system keeps logs in Kibana. I have a problem while tracking backend logs. For example after order success we call notification, report etc. services. That is one life cycle in banckend. There are more life cycles like this in the system and we need to track the movement on the system for solving problems.
How can I add some kind of traceID in request objects. Is it a characteristic?
Thanks.
#General
------------------------------
Ali Rıza Arslan
TO BE VERIFIED
------------------------------