You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EDC operations can be managed better for operators and domain managers
What are the Risks/Dependencies ?
none
Detailed explanation
Define the standard path for creating metrics during EDC operations and to forward them to a processing engine. Create a set of standard metrics usable for operators but also for domain managers to get insides into the current activities around data consumption or provisioning
Decision Record exists that describes the metric framework
First metric as defined in the user stories are implemented and available for an operator
Test Cases
Test Case 1
Steps
Run an EDC and do some data exchange
Get metrics results measured during the exchange
Expected Result
Metric results are available
The measured values are as expected
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.
This feature aligns with our current architectural guidelines
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
Additional information
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)
The text was updated successfully, but these errors were encountered:
Overview
Explain the topic in 2 sentences
Implement metrics framework and initial metrics
What's the benefit?
EDC operations can be managed better for operators and domain managers
What are the Risks/Dependencies ?
none
Detailed explanation
Define the standard path for creating metrics during EDC operations and to forward them to a processing engine. Create a set of standard metrics usable for operators but also for domain managers to get insides into the current activities around data consumption or provisioning
Feature Team
Contributor
Committer
User Stories
Acceptance Criteria
Test Cases
Test Case 1
Steps
Expected Result
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.
Additional information
The text was updated successfully, but these errors were encountered: