Re: web service logging
Date: Sat, 16 Jan 2016 01:58:27 +0300
Message-ID: <CAOVevU4SdmWWT_o2Y1KJ5PLtdCf6pDDp9=+JJO5QWSdT88vDbA_at_mail.gmail.com>
So without database connection their service will not log? :) It seems strage for me.
I think standard solution with simple log files is better. They can analyze it later with any tool or even move to hadoop :)
On Sat, Jan 16, 2016 at 1:50 AM, Jeff <backseatdba_at_gmail.com> wrote:
> I know this is not directly a DBA question but I thought maybe someone
> would have some experience.
> My web team is wanting to implement a logging service which will log all
> calls to their web services and info about who and what was called. And so
> they are wanting to store this in the database in some table or tables.
> Which basically means that every call to the database will generate an
> additional call for logging. To me this seems like a bad idea to store in
> the database. I am either thinking of creating a separate database just
> for logging or well I don't know. I suggested just writing it all to a
> file and use something like Splunk but for some reason which I haven't
> found out yet they said that would not work for them.
> Any suggestions/advice? Is this normal practice to log back to the
> database?
>
>
>
-- Best regards, Sayan Malakshinov Oracle performance tuning engineer Oracle ACE Associate http://orasql.org -- http://www.freelists.org/webpage/oracle-lReceived on Fri Jan 15 2016 - 23:58:27 CET