[Connector] Provide event information in logs

[lgblaumeiser]

Overview

Explain the topic in 2 sentences

The Tractus-X connector has an embedded event mechanism that informs potential listeners about specific incidents, like finalized contract negotiations. These events should be routed using the standard log mechanism to provide the information for further processing, e.g., in Dashboards

What's the benefit?

Better transparency of domain activities within the connector

What are the Risks/Dependencies ?

There is a relationship to the activities in TAP 7.4 of Catena-X Next, as there it is planned to route the same events as Cloud events using a standard eventing mechanism instead of the log stream.

Detailed explanation

An event listener will be implemented that receives the internal events and transforms them into a log entry. This is related to the issue https://github.com/eclipse-tractusx/sig-release/issues/1280, as the log entry would then be logged in a structured way, that allows further processing steps to work with semantically richer data.

Feature Team

Contributor

• Cofinity-X
• Schaeffler

Committer

• @lgblaumeiser

Acceptance Criteria

• Events provided by the connectors internal event mechanism are seen as structured information in the logs

Test Cases

Test Case 1

Observe the log entries for events

Steps

1. Setup a provider/consumer connector setup
2. Execute a discover/negotiate/transfer scenario

Expected Result

1. All relevant events are logged in the log stream

Architectural Relevance

The following items are ensured (answer: yes) after this issue is implemented.

In the context of the standards 126 and 127, typically only one is applicable, depending on the specific use case. Please cross out one of the two standards that does not apply.

• [x] This feature aligns with our current architectural guidelines
  • Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
  • [x] CX-0010 Business Partner Number
  • [x] CX-0013 Identity of Member Companies
  • [x] CX-0018 Data Space Connectivity (EDC)
  • [x] CX-0049 DID Document Schema
  • [x] CX-0050 Framework Agreement Credential
  • [x] CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
  • [x] CX-0001 EDC Discovery API
  • [x] CX-0002 Digital Twins in Catena-X
  • [x] CX-0018 Data Space Connectivity (EDC)
  • [x] CX-0126 Industry Core: Part Type 2.0.0
  • [x] CX-0127 Industry Core: Part Instance 2.0.0
  • Data Format:
  • [x] The data model is based on a published Semantic Model
• [x] The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
• [x] Potential risks or conflicts with existing architecture has been assessed

Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)

Additional information

• [x] I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)

[lgblaumeiser]

Hi @kkotowiczz, I added Schaeffler here, as Thomas already has some prototype for that, please inform Thomas and Siggi, as they are not an official contributor

[stephanbcbauer]

was presented during open planning for release 25.09

[th0masgl]

i created the following issue : https://github.com/eclipse-tractusx/tractusx-edc/issues/1949