Skip to content
This repository has been archived by the owner on Jan 15, 2024. It is now read-only.

Configure logging #24

Open
sondr3 opened this issue Feb 22, 2019 · 3 comments
Open

Configure logging #24

sondr3 opened this issue Feb 22, 2019 · 3 comments
Assignees
@sondr3 @Eivinddh
Labels
enhancement New feature or request

Comments

@sondr3
Copy link
Member

sondr3 commented Feb 22, 2019

No description provided.

@sondr3 sondr3 added the enhancement New feature or request label Feb 22, 2019
@sondr3 sondr3 self-assigned this Feb 22, 2019
@Eivinddh Eivinddh self-assigned this Mar 5, 2019
@Eivinddh
Copy link
Member

Eivinddh commented Mar 5, 2019

What do we want to log?
Logs can be five different states:

  • DEBUG: Low level system information for debugging
  • INFO: General system
  • WARNING: Information describing a minor problem that has
  • ERROR: Information describing a major problem that has
  • CRITICAL: Information describing a critical problem that has occurred.

@sondr3
Copy link
Member Author

sondr3 commented Mar 5, 2019

Log all the things! 🐰

The only thing I really want to log are requests to the API itself, i.e. responses (200, 404) etc, and logging what we get from the sensor itself, probably as INFO.

@Eivinddh Eivinddh mentioned this issue Mar 5, 2019
Merged
@Eivinddh
Copy link
Member

After deep, insightful discussion with Albin, we should probably log:

  • Crash/exception info
  • Debug info
  • API responses
  • ???
  • Profit

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sondr3 sondr3

@Eivinddh Eivinddh

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sondr3 @Eivinddh