Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging DB table design and add service to save all application logs into the DB table #16

Open
1 of 3 tasks
dan-du-car opened this issue Aug 27, 2022 · 0 comments
Open
1 of 3 tasks
Labels
enhancement New feature or request

Comments

@dan-du-car
Copy link
Collaborator

dan-du-car commented Aug 27, 2022

Types of Issue

  • Anomaly report (something appears to not work correctly)
  • Enhancement request (describe the enhancement being requested)
  • Other (please ensure the description clarifies why the issue doesn’t fall into either of the above categories)

Descriptive summary

To tracking any error or detailed events for the application in a centralized location and help developers to maintain and debug the applications, the application logs need to be saved to a DB table. The logging table needs to include at least below information:

  • Timestamp: when this log is generated.
  • Detailed log content: The log content provide detailed description about the events.
  • Service/Component name: Which service or component generates this log entry.
  • etc..

CDA Telematics version where this issue was discovered

Expected behavior

Any cloud application logs should be saved to a dedicated DB table.

Actual behavior

NA

Steps to reproduce the actual behavior

NA

Related work

@dan-du-car dan-du-car added the enhancement New feature or request label Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant