Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@manifoldcf.apache.org
Received-SPF: pass (athena.apache.org: domain of daddywri@gmail.com designates
 209.85.213.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALUFAGB9YWv2ttvmnc=m=w189N2vnvQUjxpFEtnRmGZJRkxALw@mail.gmail.com>
References: 
 <CAALTCc+50veG7Pw4qbKoD0eayFib1OBnzvAcQwHihWKx3L03Sg@mail.gmail.com>
	<CALUFAGDs7SbgodJ8C=R3i+xKeudX8-sKm4YR7eZmMKT1sKPOBA@mail.gmail.com>
	<1C582273-0DEA-4BCF-8682-C17BCA47175F@gmail.com>
	<CALUFAGB9YWv2ttvmnc=m=w189N2vnvQUjxpFEtnRmGZJRkxALw@mail.gmail.com>
Date: Fri, 17 Oct 2014 06:49:56 -0400
Message-ID: 
 <CALUFAGCA-ZSN5mJTPt0dbSBSVwA06RSfh9hVJn9Tssk7VzzMhA@mail.gmail.com>
Subject: Re: Logging
From: Karl Wright <daddywri@gmail.com>
To: dev <dev@manifoldcf.apache.org>
Content-Type: multipart/alternative; boundary=001a1133e48a29f95e05059c200e

--001a1133e48a29f95e05059c200e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

We *have* a feature that is cross-cluster and is meant for precisely this
purpose.  This is the history table.  If Tika exceptions are not logged as
the result of a transformation attempt in this table, they should be.

We've in general been slow to add support for activity logging in our
connectors; perhaps we should put our effort towards fixing that problem.

Thanks,
Karl


On Fri, Oct 17, 2014 at 6:46 AM, Karl Wright <daddywri@gmail.com> wrote:

> Hi Muhammed,
>
> In a cluster, where do you expect to look for the log file?  The log will
> only apply to the cluster member running the crawler UI.
>
> Karl
>
>
> On Fri, Oct 17, 2014 at 5:59 AM, Muhammed Olgun <mh.olgun@gmail.com>
> wrote:
>
>> Hi Karl,
>>
>> I think that we can also read logging.ini file from the MCF and show, fo=
r
>> instance, last 50 lines of log file.
>>
>> We can see that is the document processed or not from the document statu=
s
>> report but we cannot see that why the document isn't processed. May be
>> document isn't processed because there was a tika exception or something
>> different. We have to check the log file.
>>
>> If we can add such a feature, we will check the log file easily and we
>> won=E2=80=99t have to access the server to check the log file.
>>
>> Muhammed
>>
>>
>> On 17 Oct 2014, at 11:53, Karl Wright <daddywri@gmail.com> wrote:
>>
>> > Hi Muhammed,
>> >
>> > The problems with that idea are several:
>> >
>> > (1) You don't know where the logs are, or if/when they rolled.  All of
>> that
>> > is configured in the logging.ini file.
>> > (2) The logs may be very very large.
>> > (3) The logs are meant for a different sort of user than the typical U=
I
>> > user.
>> >
>> > The only programs I know who allow you to view logs capture them
>> explicitly
>> > themselves, for example Jenkins.
>> >
>> > It is probably far better to capture more kinds of activities in the
>> simple
>> > history than to try to provide a log viewer in the UI.  Can you descri=
be
>> > what you would want to look for?
>> >
>> > Karl
>> >
>> >
>> >
>> > On Fri, Oct 17, 2014 at 4:40 AM, Muhammed Olgun <mh.olgun@gmail.com>
>> wrote:
>> >
>> >> Hi,
>> >>
>> >> I was thinking that we should add a feature which shows manifoldcf.lo=
g
>> in
>> >> MCF's control panel. What do you think about it?
>> >>
>> >> Muhammed
>> >>
>>
>>
>

--001a1133e48a29f95e05059c200e--