DEBUG logs are wrote to /var/log/messages every 10 seconds
Description
DEBUG logs are wrote to /var/log/messages every 10 seconds. It seems nodejs(UI) generates it.
Log lever should be INFO by default
Oct 10 11:58:21 cloudify node: #033[36m[2018-10-10 11:58:21.707] [DEBUG] ServerProxy - #033[39mProxying GET request to server with url: https://127.0.0.1:53333/api/v3.1/nodes?_include=id,deployment_id&
Oct 10 11:58:21 cloudify node: #033[36m[2018-10-10 11:58:21.708] [DEBUG] ManagerHandler - #033[39mAdding CA file to Agent Options
Oct 10 11:58:21 cloudify node: #033[36m[2018-10-10 11:58:21.710] [DEBUG] ServerProxy - #033[39mProxying GET request to server with url: https://127.0.0.1:53333/api/v3.1/node-instances?_include=id,state,deployment_id&
Steps to Reproduce
Environment:
OS (CLI), HA cluster, cloud provider
------------------------------------
Steps to reproduce:
------------------
1.
2.
3.
Expected result:
---------------
Actual result:
-------------
Why Propose Close?
Activity
Sure, let’s have the same default level for everything. I’m surprised it’s not INFO, but as long as it’s consistent I think it’s reasonable.
I’d much prefer that we had the logging configuration all in one place- I understand it’ll be a little more irksome for you, but from a user/support standpoint it’s much easier to just say “Change it in this file” when there are problems.
Given that, I’d lean towards putting the configuration in that same file.
I agree with you Sandy, but I think it is not the right time. There are couple of issues with logging in UI projects:
and I hope I’ll be working on it after 5.1 release. Start using /etc/cloudify/logging.conf in UI is described as part of the last one.
As long as it’s roadmapped, I’m happy with an interim solution.
Sure. I’ll discuss that with on our next weekly meeting.
Assignee
Reporter
Severity
Target Version
Premium Only
Found In Version
QA Owner
Bug Type
Customer Encountered
Customer Name
Release Notes
Priority
Epic Link
Sprint
Priority
