Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Abstraction

This chapter provides requirements for the function of the System Logging Support.

In the use of IVI products, it is necessary to collect and centrally manage logs created in multiple places in the system, which are records of various events and times that occurred in systems. The reasons to keep logs are for security measures or information gathering and decision making in the operation, management and countermeasure for anomalies of the product system.

Use case

In the following table, use cases which need System Logging Support function are described.
As use cases, two cases need to be assumed: before and after product shipment.

#Item
1

Developers check the logs for implementation and evaluation to debug.

2

From a security perspective, OEM examines the logs to investigate whether there has been unauthorized access to the system from outside.

3

When some anomaly in the system requires a measure to a product failure, OEM investigates the cause of the problem.

#1 : Before product shipment
#2, 3 : After product shipment

Functional Requirements

This table includes the functional requirements of System Logging support module.

#Item

1

A configuration file describing the settings of the logs should be prepared. 

2

A configuration file describing the settings of the logs should be prepared.In the configuration file, the configuration file should have the following items.

  • Where to put Log archive file (ex.tar.gz)
  • Maximum number of archive files that can be left at ACC off
  • Maximum number of archive files that can be left when the system detects an error 

3

The logs which will be archived should have the following items.

  • System message log that can be acquired with dmesg
  • Error detection log

4

Considering the endurance, the log should be recorded in the volatile memory and recorded in the non-volatile memory as necessary.

5

A function to write the log recorded in the volatile memory to the nonvolatile memory should be implemented.


System Logging Support in Basesystem

Reference implementation in Basesystem

The following functions are related to the System Logging Support function in Basesystem.

  • Logger service 

Logger Service

Logger service is the unit to collect the log, save in a non-volatile area (USB/SD). When receiving the storing request, Logger service reads the log generated by other modules and saves it.

Reference code

Logger service

https://gerrit.automotivelinux.org/gerrit/gitweb?p=staging/basesystem.git;a=tree;f=service/system/logger_service;h=3b33fe43aa5914210ac1e3e485d118a9d8d103bd;hb=refs/heads/master

  • No labels