You could log that information to a document in MarkLogic. One history document for each document that is processed. --wunder
On Nov 5, 2010, at 12:46 PM, helen chen wrote: > Hi David, > > What happened here is: when the article get published, I have to do something > and move data around. I want to log the important steps and information to a > separate file, and this file will be kept as a reference in case something > wrong. This publishing can involve a few hundred articles at one time, that > means the message I'm going to create can be a lot at some point. If the > message is not much, I think web service can do it, but when I have a lot, > and those messages are from each steps, not at one time, it means I have to > call web service many many times, I'm not sure the impact of this to the > program. It sounds to me that it is going to slow down a lot. But I never > tried this way. > > In what situation did you use this way? > > Thanks, > Helen > > On Nov 5, 2010, at 3:23 PM, Lee, David wrote: > >> Another alternative is you could log to a web service. >> That requires some substantial infrastructure but it may be worth it >> depending on what your doing. >> Technically its quite easy to do, but it adds one more big piece to the >> puzzle, and depending on how frequent your logs are may slow things down >> a lot. >> >> >> ---------------------------------------- >> David A. Lee >> Senior Principal Software Engineer >> Epocrates, Inc. >> [email protected] >> 812-482-5224 >> >> >> >> >> >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of helen chen >> Sent: Friday, November 05, 2010 3:18 PM >> To: General Mark Logic Developer Discussion >> Subject: Re: [MarkLogic Dev General] question about logging >> >> Hi Wunder, >> >> Thanks for this information. I have to study it and see if I can make it >> work. >> >> Helen >> >> >> On Nov 5, 2010, at 2:58 PM, Walter Underwood wrote: >> >>> Using the admin UI, navigate to the group your hosts are in. On that >> page, near the bottom, there is an choice for "system log level". That >> chooses what level of log events will be sent to the system log. On >> Unix, that is syslog. There is a separate choice for "file log level", >> which controls what is logged in ErrorLog.txt. >>> >>> syslog_ng can use patterns to match log messages and route them to a >> particular log. >>> >>> wunder >>> >>> On Nov 5, 2010, at 11:44 AM, helen chen wrote: >>> >>>> Hi Walter, >>>> >>>> When you say "configure MarkLogic so the system log level includes >> your extra log messages", where can I do the configuration? Does that >> mean the log that write to ErrorLog.txt will also be written to syslog? >> is there any special format that I need to do for the message that I >> want to log? If it is in some document, can you point me which document >> I can find it? >>>> >>>> Thanks, Helen >>>> >>>> >>>> On Nov 5, 2010, at 1:37 PM, Walter Underwood wrote: >>>> >>>>> If you are on a system that uses syslog_ng, you can do this with >> that tool. >>>>> >>>>> Log messages normally, but configure MarkLogic so the system log >> level includes your extra log messages. Configure syslog_ng to route >> those log messages to the file you want. >>>>> >>>>> wunder >>>>> == >>>>> Walter Underwood >>>>> [email protected] >>>>> >>>>> On Nov 5, 2010, at 8:33 AM, helen chen wrote: >>>>> >>>>>> Maybe I didn't say it clearly. >>>>>> >>>>>> fn:concat() is for the message part. I also want to write this >> message to a separate file on the file system, the file name is >> specified dynamically. And if this file already exists on file system, >> it should be the append , not overwrite. It is similar to the unix >> script that I write my log to some file I want. >>>>>> >>>>>> In the meantime I don't want to stop the xdmp:log(), if I use >> xdmp:log, it should still write to ErrorLog.txt file. >>>>>> >>>>>> Thanks, Helen >>>>>> >>>>>> >>>>>> >>>>>> On Nov 5, 2010, at 11:19 AM, Tim Meagher wrote: >>>>>> >>>>>>> I just embed fn:concat() within the call the xdmp:log() and >> concatenation >>>>>>> the various message parts, e.g. >>>>>>> >>>>>>> xdmp:log(concat("Path: ", {$path})) >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: [email protected] >>>>>>> [mailto:[email protected]] On Behalf Of >> helen chen >>>>>>> Sent: Friday, November 05, 2010 11:16 AM >>>>>>> To: General Mark Logic Developer Discussion >>>>>>> Subject: [MarkLogic Dev General] question about logging >>>>>>> >>>>>>> Hello there, >>>>>>> >>>>>>> In Marklogic, I use xdmp:log() to log message to ErrorLog.txt >> file. I want >>>>>>> to do some logging similar to script, like I specify the path and >> file name, >>>>>>> then I write just the message I want to this file and then keep >> appending >>>>>>> message to this file. I expect that this should not stop the >> normal logging >>>>>>> of xdmp:log(). >>>>>>> >>>>>>> Does anyone have suggestion on how to do it? >>>>>>> >>>>>>> Thanks, Helen >>>>>>> _______________________________________________ >>>>>>> General mailing list >>>>>>> [email protected] >>>>>>> http://developer.marklogic.com/mailman/listinfo/general >>>>>>> >>>>>>> _______________________________________________ >>>>>>> General mailing list >>>>>>> [email protected] >>>>>>> http://developer.marklogic.com/mailman/listinfo/general >>>>>> >>>>>> _______________________________________________ >>>>>> General mailing list >>>>>> [email protected] >>>>>> http://developer.marklogic.com/mailman/listinfo/general >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> General mailing list >>>>> [email protected] >>>>> http://developer.marklogic.com/mailman/listinfo/general >>>> >>>> _______________________________________________ >>>> General mailing list >>>> [email protected] >>>> http://developer.marklogic.com/mailman/listinfo/general >>> >>> -- >>> Walter Underwood >>> [email protected] >>> >>> >>> >>> _______________________________________________ >>> General mailing list >>> [email protected] >>> http://developer.marklogic.com/mailman/listinfo/general >> >> _______________________________________________ >> General mailing list >> [email protected] >> http://developer.marklogic.com/mailman/listinfo/general >> _______________________________________________ >> General mailing list >> [email protected] >> http://developer.marklogic.com/mailman/listinfo/general > > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general -- Walter Underwood [email protected] _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
