Collecting logging information for 3rd party systems

Sometimes you may wish to collect logging information for use in 3rd party reporting and monitoring systems, e.g. Splunk.

The following query gives the crucial information for each log message:

select
       lf.name as task_name,
       lf.start_dtm as task_start_dtm,
       lf.end_dtm as task_end_dtm,
       lu.first_name || ' ' || lu.last_name as local_user_name,
            eu.first_name || ' ' || eu.last_name as domain_user_name,
            lf.complete_boo as task_complete_boo,
            lm.message_type,
            lm.message
from
    log_file lf
    inner join log_message lm on
        lf.log_file_id = lm.log_file_id
    left outer join local_user lu on
        lf.user_id = lu.user_id
    left outer join external_user eu on
        lf.user_id = eu.user_id

To run this query you will need read access to the following tables in the PhixFlow schema:

• log_file
• log_message
• local_user
• external_user

The following message types (m.message_type) are found in PhixFlow log files:

• WARNING
• DEBUG
• ERROR
• INFO

The task_name field in the results will be one of:

• A task plan name, if a task plan was run directly or under a schedule
• A stream name, if a stream was run directly (for example, from a model view)
• An action name, if an streamAction triggered the task plan

This is simply what appears in the Name field of the Active Tasks and Completed Tasks windows in the System Console.