Component Architecture Documentation

Logging Backend Architecture		status: draft security: NO safety: ASIL_B
version: 1 realizes: wp__component_arch
doc__logging_backend_architecture		Generic Document

Overview

Supports logging on several backends (file,slog,remote,custom)

Description

<General Description>

<Design Decisions - For the documentation of the decision the gd_temp__change_decision_record can be used.>

<Design Constraints>

Rationale Behind Architecture Decomposition

Mandatory: A motivation for the decomposition or reason for not further splitting it into internal components.

Note

Common decisions across components / cross cutting concepts is at the higher level.

Static Architecture

The components are designed to cover the expectations from the feature architecture (i.e. if already exists a definition it should be taken over and enriched).

A component can optional also consist of lower level components to further structure the architecture. The component and its static views can also optionally use interfaces provided by other components.

Logging Backend		status: valid security: YES safety: ASIL_B
version: 0 belongs to: feat__logging has: comp_arc_sta__log__sv implements: logic_arc_int__log_cpp__logging included by: mod__logging_repo, mod_view_sta__logging__static_view
This is the logging component library responsible for selecting the appropriate log sinks based on configuration at runtime. It can perform tasks such as log formatting, filtering, and composite backend selection based on runtime context and configuration. The logging component is designed to be extensible, allowing for custom logging backend to be added as needed.
comp__logging_backend		Component

Logging Backend (Static View)		status: valid security: YES safety: ASIL_B
version: 1 belongs to: comp__logging_backend fulfils: comp_req__log__local_allocation_strategy
comp_arc_sta__log__sv		Component Package Diagram

Dynamic Architecture

not needed

Interfaces

not needed