Skip to content

tables logs_setup

Jan Kvetina edited this page Oct 10, 2020 · 12 revisions

logs_setup table

Source code: logs_setup

Description of table which is used to adjust what is logged and what not.

ID Column name Data type NN UQ FK Comment
1 app_id NUMBER(4) Y Y App ID; 0 for no APEX, NULL for any app
2 page_id NUMBER(6) Y APEX page ID; NULL for any page
3 user_id VARCHAR2(30) Y Y User ID; NULL or % for any user
4 role_id VARCHAR2(30) Y Y Role ID; NULL or % for any role
5 flag CHAR(1) Y Flag to differentiate logs; NULL for any flag
6 module_name VARCHAR2(30) Y Module name; NULL for any module
7 is_tracked CHAR(1) Y Y = track; N = dont track; Y > N

You can adjust tracking for specific users, flags and/or modules by using blacklisted or whitelisted records.
Whitelisted row (track = 'Y') precedes blacklisted (track = 'N') row and you can use % as LIKE in SQL.

Combination is evaluated by tree.is_listed function in tree package init block, resp. in tree.log__ function.


logs_setup.user_id

User id with % as possible wild flag (LIKE clause).


logs_setup.module_name

Module name (package.procedure/function) with % as possible wild flag (LIKE clause).


logs_setup.flag

Flag from tree package specification with % as possible wild flag (LIKE clause).


Data examples

Log specific flag only for some users

User_id Module_name Flag Track Description
% % D N Ignore D flagged logs for all users and all modules
USER_A % D Y Store D logs for USER_A
USER_B % D Y Store D logs for USER_B

Log specific flag only for some modules

User_id Module_name Flag Track Description
% % D N Ignore D flagged logs for all users and all modules
% APP.% D Y Store D logs from APP package

Clone this wiki locally