Re: Creating a comprehensive log file

Are you asking about modifying someone else's script to do this or is this just functionality that you want to add to your own scripts, or what?

I'm asking because errors and warnings should probably be printed on stderr, not stdout. So, if this is for your own script then stop writing errors to an inconvenient place and you'll be half-way there. The other half would be to have an error handler that sent the messages to wherever you wanted. Choices would probably include stderr, a logfile, or both. I think there are some modules around that would help with exactly that...

I'm reluctant to answer your question with code because I believe the question that needs to be answered here isn't quite the one you are asking. Can you explain your problem further?

Wow. This was my 1500th post.

-sauoq
"My two cents aren't worth a dime.";

Comment on Re: Creating a comprehensive log file

Replies are listed 'Best First'.
Re^2: Creating a comprehensive log file by juo (Curate) on Dec 16, 2004 at 06:05 UTC
I created a customized log file which contains information as I want it to get into the log file. Some example can be seen below. `WriteLog("PROJECTCONTROL","INFO",'ID1252',"Project Name is \<$project_ +name\>"); WriteLog("PROJECTCONTROL","INFO",'ID1250',"Datasource of this job was +\<$datasources\>"); sub WriteLog { my ($script,$type,$id,$log) = @_; $logfile = $job_path.'/user/LogFile.txt'; my $logdate = $today; my $loguser = $USERNAME; open (LOG, ">>$logfile") \|\| die "File does not exist\n"; print LOG "$script $type $id $loguser $logdate $log\n"; close (LOG); }` [download] This works very nice and I can now from the log file know what exactly is happening and where something is in the process and which script is running and if something failed upto which point something had ran fine. However in case something fails what I will not get into this file is the failure message which will be returned by Perl, or an application or anything else, which is mostly returned to the STDOUT screen. So I see they are some modules maybe available to do this but I would like to stick to my customized log file and just would like to add the warning and errors which would be provided by Perl itself to it. I don't know if this is possible in an easy way.	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Creating a comprehensive log file
by juo (Curate) on Dec 16, 2004 at 06:05 UTC

I created a customized log file which contains information as I want it to get into the log file. Some example can be seen below.

WriteLog("PROJECTCONTROL","INFO",'ID1252',"Project Name is \<$project_
+name\>");
WriteLog("PROJECTCONTROL","INFO",'ID1250',"Datasource of this job was 
+\<$datasources\>");


sub WriteLog
{
 my ($script,$type,$id,$log) = @_;
 $logfile = $job_path.'/user/LogFile.txt';
 my $logdate = $today;
 my $loguser = $USERNAME;
 open (LOG, ">>$logfile") || die "File does not exist\n";
  print LOG "$script $type $id $loguser $logdate   $log\n";
  close (LOG);
}
[download]

This works very nice and I can now from the log file know what exactly is happening and where something is in the process and which script is running and if something failed upto which point something had ran fine. However in case something fails what I will not get into this file is the failure message which will be returned by Perl, or an application or anything else, which is mostly returned to the STDOUT screen. So I see they are some modules maybe available to do this but I would like to stick to my customized log file and just would like to add the warning and errors which would be provided by Perl itself to it. I don't know if this is possible in an easy way.

[reply]
[d/l]