Skip to content
This repository has been archived by the owner on Jul 12, 2023. It is now read-only.

Problem: logging defaults to DEBUG #16

Open
sevein opened this issue Nov 29, 2017 · 0 comments
Open

Problem: logging defaults to DEBUG #16

sevein opened this issue Nov 29, 2017 · 0 comments
Labels
Type: feature New functionality.

Comments

@sevein
Copy link
Member

sevein commented Nov 29, 2017

I think this is true for all the components: MCPServer, MCPClient, Dashboard and Storage Service. They all have a console handler with the level set to DEBUG. I think that we should change that to WARNING or INFO because that's what you want in production. Our Compose environment would inject config to change it to DEBUG but that's something that our settings module don't support yet.

This is not a problem in packages or Ansible because they populate their own configuration system to reproduce the old AM16 behaviour.

@sevein sevein self-assigned this Nov 29, 2017
@sevein sevein modified the milestone: v1.8.0 Dec 7, 2017
@sevein sevein added the Type: feature New functionality. label Dec 7, 2017
@sevein sevein removed their assignment May 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: feature New functionality.
Projects
None yet
Development

No branches or pull requests

1 participant