On 03/05/11 10:04, Eystein Måløy Stenberg wrote:
Have you looked in the reference manual at all?
All components log errors to syslog by default.
did you actually read my message? afaict you did not, but i made a
special point to read yours and test your suggestions.
Searching for "syslog" in the reference shows lots of options regarding logging.
A few quick hits on logging:
http://www.cfengine.org/manuals/cf3-reference.html#Logs-and-records
http://www.cfengine.org/manuals/cf3-reference.html#syslog-in-agent
http://www.cfengine.org/manuals/cf3-reference.html#action-in-_002a
(see log_level)
http://www.cfengine.org/manuals/cf3-reference.html#logallconnections-in-server
http://www.cfengine.org/manuals/cf3-reference.html#agentfacility-in-agent
http://www.cfengine.org/manuals/cf3-reference.html#inform-in-agent
http://www.cfengine.org/manuals/cf3-reference.html#verbose-in-agent
it's pretty clear that all these links contain the word "log" and are
indeed in the reference manual. i already set the cf-serverd ones but i
figured i should test your suggestions for the cf-agent settings. well,
i did test them and they do not log what i stated in my earlier email i
wanted to log:
"the various cf-* daemons work great in the foreground with verbose or
debug outputs. unless i am really missing something it seems that it has
been made intentionally difficult to get this same information to write
to a log."
what i am really after is logging changes in promise status i.e. this
promise was repaired, this one wasn't, etc. amusingly enough your first
link pointed me right at the data i had alluded to but not found direct
reference to:
cf_notkept.log
A list of promises, with handles and comments, that were not kept.
Nova enterprise versions only.
cf_repaired.log
A list of promises, with handles and comments, that were repaired.
Nova enterprise versions only.
from section 13.2. this tells me that i must make a report entry for
every promise that i want to log and that the global switch to turn this
on or off is only in cfengine nova, as per my claims.
i must say that i am a bit shocked at where the cfengine folks have
chosen to draw the line between normal open source and the licensed
version. being a businessperson myself, i understand the desire or need
to monetize a project or idea in order to propel it forward. removing
what most people would consider basic functionality, e.g. system wide
logging options, strikes me as a particularly poor choice for where to
draw the line. other open source projects take a similar tack but do not
release crippled code, e.g. request tracker, where, imo, the
documentation is intentionally poor to encourage people to pay for
consulting services, classes, etc. i suspect far fewer people would end
up using RT if it had basic functionality removed, e.g. you could not
make comments and only reply to tickets.
after looking at cfengine and puppet i really thought cfengine was the
clear winner for my use case since it's written in C and doesn't have
tons of ruby deps. now i have to rethink that choice based on the manner
in which cfengine and puppet are monetized and check if their sources
are correspondingly crippled. it's not even about the money as much as
the business decision of making a crippled product available and
expecting people to then pay you money to "uncripple" it. if this is the
business strategy out of the box for potential new customers it does not
bode well for future interactions.
I think you should be careful about making strong claims/complaints
without checking the facts first. Perhaps writing a separate document
on logging is a good idea, but we already have so much documentation
that it might not help people find it faster anyway.
As a side note, if you truly were interested in buying Nova, you will
get a free trial easily by filling out the form at
http://cfengine.com/pages/contactUs
Happy hacking.
--
Regards,
Eystein
On Sat, Mar 5, 2011 at 4:03 PM, Jake<behindt...@gmail.com> wrote:
On 03/04/11 07:53,no-re...@cfengine.com wrote:
Forum: Cfengine Help
Subject: Re: proper logging for cfengine processes
Author: neilhwatson
Link to topic:https://cfengine.com/forum/read.php?3,20915,20955#msg-20955
Nova has the best logging built in. For community you have to do more work. I
use report promises extensively. When the agent is run from the executor these
reports go to syslog.
thanks for this info, there is very little info to go on.
after searching for further information on this topic (logging) i am
left to conclude i am pretty much screwed with cfengine 3 community. i
cannot speak on cfengine nova. i would like to think that i am wrong but
your comment suggests to me that "if you want real logging, you must
pay" which is, imo, ridiculous.
the various cf-* daemons work great in the foreground with verbose or
debug outputs. unless i am really missing something it seems that it has
been made intentionally difficult to get this same information to write
to a log. this is unbelievably stupid and could easily be fixed with an
hour or two of developer work, but i would be willing to bet a patch
would not be accepted. this seems like a *really* poor choice of
features to intentionally remove from the unpaid version of the software.
without proper logs one really cannot gauge how well the community
solution works for their application. removal of the basic features
required to test the real world utility of the software make a potential
purchaser (me) unlikely to proceed with any purchase because the quality
of the goods on display is questionable.
there should be a couple simple settings for logging in each daemon's
config file e.g.
syslog = yes
log_level = 3
the apparent lack of any such settings or any accompanying documentation
is pretty shocking.
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
