Re: Query logging - PHOENIX-2715
Log level has four levels: OFF, INFO, DEBUG, and TRACE, the default value of log level is OFF. we can config by setting "phoenix.log.level" to log each query on the client side. Jaanai Zhang Best regards! M. Aaron Bossert 于2019年4月20日周六 上午8:12写道： > Sorry if I have missed something obvious, but I saw that this was > implemented (according to JIRA) in 4.14 and 5.0.0. I need to set this up > to log each query in that SYSTEM:LOG table, but cannot seem to find the > official instructions for how to configure this through LOG4J settings or > whatever it is now. Could someone please point me in the right direction? > > On Tue, Nov 20, 2018 at 9:31 PM Jaanai Zhang > wrote: > >> yep! That configuration options do not exist. >> >> >>Jaanai Zhang >>Best regards! >> >> >> >> Curtis Howard 于2018年11月20日周二 下午11:42写道： >> >>> Hi Jaanai, >>> >>> Thanks for your suggestion. Just confirming then - it sounds like this >>> would involve adding custom code, as there are no current configuration >>> options to enable logging/capture of all query statements (including >>> DDL/DML) from clients? >>> >>> Thanks for your help >>> Curtis >>> >>> On Tue, Nov 20, 2018 at 8:33 AM Jaanai Zhang >>> wrote: >>> We can't capture some detail information about the DDL/DML operations by TRACE log. I suggest that you can print logs of these operations on the logic layer. Jaanai Zhang Best regards! Curtis Howard 于2018年11月20日周二 上午11:20写道： > Hi, > > Is the expected behavior for this new feature to capture all > operations (UPSERT / DROP / CREATE / ...)? After enabling > phoenix.log.level=TRACE, I see only SELECT queries populated in the > SYSTEM.LOG table. > > Thanks! > Curtis > >
Re: Query logging - PHOENIX-2715
Sorry if I have missed something obvious, but I saw that this was implemented (according to JIRA) in 4.14 and 5.0.0. I need to set this up to log each query in that SYSTEM:LOG table, but cannot seem to find the official instructions for how to configure this through LOG4J settings or whatever it is now. Could someone please point me in the right direction? On Tue, Nov 20, 2018 at 9:31 PM Jaanai Zhang wrote: > yep! That configuration options do not exist. > > >Jaanai Zhang >Best regards! > > > > Curtis Howard 于2018年11月20日周二 下午11:42写道： > >> Hi Jaanai, >> >> Thanks for your suggestion. Just confirming then - it sounds like this >> would involve adding custom code, as there are no current configuration >> options to enable logging/capture of all query statements (including >> DDL/DML) from clients? >> >> Thanks for your help >> Curtis >> >> On Tue, Nov 20, 2018 at 8:33 AM Jaanai Zhang >> wrote: >> >>> We can't capture some detail information about the DDL/DML operations by >>> TRACE log. I suggest that you can print logs of these operations on the >>> logic layer. >>> >>> >>>Jaanai Zhang >>>Best regards! >>> >>> >>> >>> Curtis Howard 于2018年11月20日周二 上午11:20写道： >>> Hi, Is the expected behavior for this new feature to capture all operations (UPSERT / DROP / CREATE / ...)? After enabling phoenix.log.level=TRACE, I see only SELECT queries populated in the SYSTEM.LOG table. Thanks! Curtis
Re: Query logging - PHOENIX-2715
yep! That configuration options do not exist. Jaanai Zhang Best regards! Curtis Howard 于2018年11月20日周二 下午11:42写道： > Hi Jaanai, > > Thanks for your suggestion. Just confirming then - it sounds like this > would involve adding custom code, as there are no current configuration > options to enable logging/capture of all query statements (including > DDL/DML) from clients? > > Thanks for your help > Curtis > > On Tue, Nov 20, 2018 at 8:33 AM Jaanai Zhang > wrote: > >> We can't capture some detail information about the DDL/DML operations by >> TRACE log. I suggest that you can print logs of these operations on the >> logic layer. >> >> >>Jaanai Zhang >>Best regards! >> >> >> >> Curtis Howard 于2018年11月20日周二 上午11:20写道： >> >>> Hi, >>> >>> Is the expected behavior for this new feature to capture all operations >>> (UPSERT / DROP / CREATE / ...)? After enabling phoenix.log.level=TRACE, I >>> see only SELECT queries populated in the SYSTEM.LOG table. >>> >>> Thanks! >>> Curtis >>> >>>
Re: Query logging - PHOENIX-2715
Hi Jaanai, Thanks for your suggestion. Just confirming then - it sounds like this would involve adding custom code, as there are no current configuration options to enable logging/capture of all query statements (including DDL/DML) from clients? Thanks for your help Curtis On Tue, Nov 20, 2018 at 8:33 AM Jaanai Zhang wrote: > We can't capture some detail information about the DDL/DML operations by > TRACE log. I suggest that you can print logs of these operations on the > logic layer. > > >Jaanai Zhang >Best regards! > > > > Curtis Howard 于2018年11月20日周二 上午11:20写道： > >> Hi, >> >> Is the expected behavior for this new feature to capture all operations >> (UPSERT / DROP / CREATE / ...)? After enabling phoenix.log.level=TRACE, I >> see only SELECT queries populated in the SYSTEM.LOG table. >> >> Thanks! >> Curtis >> >>
Re: Query logging - PHOENIX-2715
We can't capture some detail information about the DDL/DML operations by TRACE log. I suggest that you can print logs of these operations on the logic layer. Jaanai Zhang Best regards! Curtis Howard 于2018年11月20日周二 上午11:20写道： > Hi, > > Is the expected behavior for this new feature to capture all operations > (UPSERT / DROP / CREATE / ...)? After enabling phoenix.log.level=TRACE, I > see only SELECT queries populated in the SYSTEM.LOG table. > > Thanks! > Curtis > >
Query logging - PHOENIX-2715
Hi, Is the expected behavior for this new feature to capture all operations (UPSERT / DROP / CREATE / ...)? After enabling phoenix.log.level=TRACE, I see only SELECT queries populated in the SYSTEM.LOG table. Thanks! Curtis
