Hi David and Mike,

The file log level specifies the log level for the ErrorLog.txt file, and it 
does that on a group setting, so it is not a one-time thing.

The only way I know of to log queries is to do so at the application level, 
which it sounds like you are already doing.  The access logs are really for the 
http and xdbc requests, and do not have other information about the content of 
the requests.  For many application, however, you might be able to 
reverse-engineer the queries based on the request URL in the access log.  For 
example, if you have a request parameter called query and its value is what the 
user entered in the text field, then you could probably figure out what that 
query is. 

Logging the actual XQuery text of every query can get expensive in production, 
and make your logs get very large very quickly.  If you want to get metrics 
like those from query-meters, that also does not come for free (and can 
generate a lot of output).  This might be acceptable depending on your 
workload, though, you would have to experiment to see how it does.  If you log 
via xdmp:log, you can be very specific about what you log, making it easy for 
some script to pick up bad stuff you might be looking for.

-Danny

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of David Sewell
Sent: Friday, April 17, 2009 7:04 AM
To: General Mark Logic Developer Discussion
Cc: Scott Cipriano
Subject: Re: [MarkLogic Dev General] Logging queries

On a server-wide basis you can configure "system log level" in the Admin
setup under Groups - Default - Configure. And it appears that on a
per-query basis you could use admin:group-set-file-log-level():

http://xqzone.com/pubs/4.0/apidocs/AdminLibraryGroup.html#admin:group-set-file-log-level

but I don't have any experience actually using it.

On Fri, 17 Apr 2009, Mike Sokolov wrote:

> Does anybody know whether there is any way to configure Mark Logic to save
> more information to its access logs?  In particular we'd like to be able to
> see query metrics; at a bare minimum, we need to know how long a query took.
> Ideally we would also like to be able to get detailed query logging showing
> the queries that are being performed, and all their arguments.  Any additional
> metrics, like # fragments, memory required, etc would be gravy.
>
> We've built support for something this in our application, but need to support
> multiple products administered by different vendors and it would be great if
> we could control logging centrally using MarkLogic admin tools.  We want this
> to be turned on and off without modifying the queries themselves or the
> applications that invoke them.
>
> So - is this possible?  In 3.2? In 4.0?  Is it coming?
>
> any suggestions appreciated
>
> -Mike Sokolov
> _______________________________________________
> General mailing list
> [email protected]
> http://xqzone.com/mailman/listinfo/general
>

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 801079, Charlottesville, VA 22904-4318 USA
Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903
Email: [email protected]   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://xqzone.com/mailman/listinfo/general

Reply via email to