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 mh.olgun@gmail.com designates
 74.125.82.45 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Logging
From: Muhammed Olgun <mh.olgun@gmail.com>
In-Reply-To: 
 <CALUFAGCA-ZSN5mJTPt0dbSBSVwA06RSfh9hVJn9Tssk7VzzMhA@mail.gmail.com>
Date: Fri, 17 Oct 2014 14:53:40 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0395CFE-DC65-40D6-83A4-60C0A19C92B4@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>
 <CALUFAGCA-ZSN5mJTPt0dbSBSVwA06RSfh9hVJn9Tssk7VzzMhA@mail.gmail.com>
To: dev@manifoldcf.apache.org

Hi Karl,

You are right. Thank you.

Muhammed=20

On 17 Oct 2014, at 13:49, Karl Wright <daddywri@gmail.com> wrote:

> 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.
>=20
> 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.
>=20
> Thanks,
> Karl
>=20
>=20
> On Fri, Oct 17, 2014 at 6:46 AM, Karl Wright <daddywri@gmail.com> =
wrote:
>=20
>> Hi Muhammed,
>>=20
>> 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.
>>=20
>> Karl
>>=20
>>=20
>> On Fri, Oct 17, 2014 at 5:59 AM, Muhammed Olgun <mh.olgun@gmail.com>
>> wrote:
>>=20
>>> Hi Karl,
>>>=20
>>> I think that we can also read logging.ini file from the MCF and =
show, for
>>> instance, last 50 lines of log file.
>>>=20
>>> We can see that is the document processed or not from the document =
status
>>> 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.
>>>=20
>>> If we can add such a feature, we will check the log file easily and =
we
>>> won=92t have to access the server to check the log file.
>>>=20
>>> Muhammed
>>>=20
>>>=20
>>> On 17 Oct 2014, at 11:53, Karl Wright <daddywri@gmail.com> wrote:
>>>=20
>>>> Hi Muhammed,
>>>>=20
>>>> The problems with that idea are several:
>>>>=20
>>>> (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 UI
>>>> user.
>>>>=20
>>>> The only programs I know who allow you to view logs capture them
>>> explicitly
>>>> themselves, for example Jenkins.
>>>>=20
>>>> 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 =
describe
>>>> what you would want to look for?
>>>>=20
>>>> Karl
>>>>=20
>>>>=20
>>>>=20
>>>> On Fri, Oct 17, 2014 at 4:40 AM, Muhammed Olgun =
<mh.olgun@gmail.com>
>>> wrote:
>>>>=20
>>>>> Hi,
>>>>>=20
>>>>> I was thinking that we should add a feature which shows =
manifoldcf.log
>>> in
>>>>> MCF's control panel. What do you think about it?
>>>>>=20
>>>>> Muhammed
>>>>>=20
>>>=20
>>>=20
>>=20