Logging

Meetup2apricot logs its activity to a log file and optionally to the console (stderr). Command line flags control which log messages should be directed to which destinations.

Log Destinations

By default, meetup2apricot writes log messages to file meetup2apricot.log in the current directory. Logs are rotated daily; five days of logs are retained.

The -l option can specify an alternate path to the log file. The -v option adds console output. The -w option, intended for cron jobs, adds console output and limits the console log level to warnings and errors. In the rare situation when meetup2apricot -w reports a warning or error, cron will send an email.

Table 2 summarizes the impact of the -l, -v, and -w flags on log destination.

Table 2. Selection of Log Destination by Command Line Flags

Log Destination	Default	-v	-w	-l logfile
Console Log Output		+	+
meetup2apricot.log	✔
Specified logfile				✔

Log Levels

By default, meetup2apricot logs only info, warning, and error messages. The -d option adds debug level messages, which help software developers. As described above, the -w option adds console output and limits the console log level to warnings and errors. Table 3 summarizes the log levels and the impact of the -d and -w flags.

Table 3. Selection of Log Level by Command Line Flags

Log Level	Reports	Default	-d	-w
Error	Failures	✔	✔	✔
Warning	Abnormal conditions	✔	✔	✔
Info	Routine operations	✔	✔
Debug	Developer details		✔