Ticket #768 (new defect)

Opened 4 weeks ago

Last modified 2 weeks ago

improve bcfg2-client logging

Reported by: somekool <somekool@…> Owned by: desai
Priority: major Milestone: Bcfg2 1.1.0 Release
Component: bcfg2-client Version: 0.9.x
Keywords: Cc:

Description

i just discovered bcfg2-client had logging capability. it is great. but it does not log what I had excepted.

unless you are running -v it will not log if you applied a config file, executed an action, installed a package or if bcfg2 automatically reloaded a service. and it is the information I would need to have logged. what did bcfg2 changed.

i don't need to log the checks. DBStats and Snapshots are there for that already. I need to know what somebody might have changed when running bcfg2 without argument or with -I or -b

so if I execute a dryrun with -n ; i dont need to see anything in the log.

I tried running -I and applying a file

it logged the following

Bcfg2.Client.Frame[24096]: The following entries are not handled by any tool:
Bcfg2.Client.Frame[24096]: ['Package:None:certmaster', 'Package:None:func', 'Package:None:ovaldi', 'Package:None:xerces-j2', 'Package:None:xerces-j2-scripts', 'Service:None:samhain']
Bcfg2.Client.Frame[24096]:

this information is in dbstat. I would prefer to know that I changed a config file and that a service has been restarted.

i tried running -n

it logged the same.

which I believe is wrong.

I tried -d and -v and there is WAY TOO MUCH output.

it looks like logging had to be implemented (maybe before dbstats was created) and it was done and never changed.

i think it should not log any checks done. no system status. only changes made by bcfg2. or please make it an option.

thanks

Attachments

Change History

Changed 4 weeks ago by solj

  • milestone changed from Bcfg2 1.0.0 Release to Bcfg2 1.0.1 Release

Changed 2 weeks ago by solj

  • milestone changed from Bcfg2 1.0.1 Release to Bcfg2 1.1.0 Release

Add/Change #768 (improve bcfg2-client logging)

Author



Change Properties
<Author field>
Action
as new
 
Note: See TracTickets for help on using tickets.