[TRACE-X] 🌟🚀 Monitoring performance metrics of the TRACE-X release 24.8

[mkanal]

Overview

Explain the topic in 2 sentences

To effectively assess and evaluate the performance of the IRS and depending on system components (EDC, dDTR, Submodel Servers), defines scenarios, performance tests, and monitoring is implemented to identify bottlenecks and detect areas where performance optimization would be most efficient.

What's the benefit?

Effectively assessing and evaluating the performance of the IRS

What are the Risks/Dependencies ?

• Nothing to report

Detailed explanation

Current implementation

Proposed improvements

Feature Team

Contributor

• Cofinity-X @rogocof
• Cofinity-X @mkanal

Committer

• @ds-jhartmann
• @ds-mwesener
• @ds-lcapellino

---

User Story

To effectively assess and evaluate the performance of the IRS and depending on system components (EDC, dDTR, Submodel Servers), defines scenarios, performance tests, and monitoring is implemented to identify bottlenecks and detect areas where performance optimization would be most efficient.

Hints

See https://github.com/eclipse-tractusx/item-relationship-service/tree/main/irs-load-tests for the existing Gatling tests.

Acceptance Criterias

• [ ] Trace-X provides Prometheus to exposure system resources and metrics

---

Test Cases

Test Case 1

Steps

1. Do something
2. Click something
3. Add something

Expected Result

1. Expectation
2. Expectation
3. Expectation

Architectural Relevance

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

• [ ] 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)
  • [ ] CX-0010 Business Partner Number
  • [ ] CX-0013 Identity of Member Companies
  • [ ] CX-0018 Data Space Connectivity (EDC)
  • [ ] CX-0049 DID Document Schema
  • [ ] CX-0050 Framework Agreement Credential
  • [ ] CX-0149 Verified Company Identity
  • Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
  • [ ] CX-0001 EDC Discovery API
  • [ ] CX-0002 Digital Twins in Catena-X
  • [ ] CX-0018 Data Space Connectivity (EDC)
  • Data Format:
  • [ ] The data model is based on a published Semantic Model
• [ ] 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
• [ ] 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)

[rogocof]

@mkanal We need to rewrite the story a little bit. Accessing Cofinity-X Grafana is not in scope here. We should provide only the capability of exposing prometheus metrics

[mkanal]

@rogocof I have removed the Grafana part. Exposing metrics and system resources via Prometheus is now the feature to be proposed.

[stephanbcbauer]

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

• Status currently in Backlog -> Since for Backlog some requirements are missing ... please update them
• Please add missing sections from the feature template, or fill them out
• Please add assignee (overall responsible person who drives the feature)