How to enable the debug logging for FE application when running or starting the application binary?
book
Article ID: KB0077713
calendar_today
Updated On:
Description
The debug logs are essential when you are facing the issues at runtime. To identify & verify the details of the activity and its input/output, debug logs plays an important role.
Resolution
To enable the debug logs for FE application at the startup please use the following way:
- Run the application binary with flogo_log_level param as given below,
FLOGO_LOG_LEVEL=DEBUG ./<application_Name>.sh
The application will start and will have debug logs enabled. To can see the debug logs similar to below example,
Ex. FLOGO_LOG_LEVEL=DEBUG ./FileUpload-linux_amd64
mpandav@mpandav-u52:~/$ FLOGO_LOG_LEVEL=DEBUG ./FileUpload-linux_amd64
2019-07-24T13:26:41.011+0530 DEBUG [flogo] - Registering function package: github.com/project-flogo/core/data/expression/function/builtin
2019-07-24T13:26:41.013+0530 DEBUG [flogo] - Registering schema factory: json
2019-07-24T13:26:41.013+0530 DEBUG [flogo] - Registering function package: git.tibco.com/git/product/ipaas/wi-contrib.git/function/array
2019-07-24T13:26:41.013+0530 DEBUG [flogo] - Registering function package: git.tibco.com/git/product/ipaas/wi-contrib.git/function/boolean
2019-07-24T13:26:41.014+0530 DEBUG [flogo] - Registering function package: git.tibco.com/git/product/ipaas/wi-contrib.git/function/datetime
2019-07-24T13:26:41.014+0530 DEBUG [flogo] - Registering function package: git.tibco.com/git/product/ipaas/wi-contrib.git/function/float
2019-07-24T13:26:41.014+0530 DEBUG [flogo] - Registering function package: git.tibco.com/git/product/ipaas/wi-contrib.git/function/number
2019-07-24T13:26:41.014+0530 DEBUG [flogo] - Registering function package: git.tibco.com/git/product/ipaas/wi-contrib.git/function/string
2019-07-24T13:26:41.014+0530 DEBUG [flogo] - Registering function package: git.tibco.com/git/product/ipaas/wi-contrib.git/function/utility
2019-07-24T13:26:41.014+0530 DEBUG [flogo] - Registering action: github.com/project-flogo/flow
2019-07-24T13:26:41.014+0530 DEBUG [function-registry] - Registry function name length tag array
2019-07-24T13:26:41.014+0530 DEBUG [function-registry] - Registry function name random tag number
2019-07-24T13:26:41.014+0530 DEBUG [function-registry] - Registry function name concat tag string
2019-07-24T13:26:41.014+0530 DEBUG [function-registry] - Registry function name equals tag string
2019-07-24T13:26:41.014+0530 DEBUG [function-registry] - Registry function name equalsIgnoreCase tag string
2019-07-24T13:26:41.014+0530 DEBUG [function-registry] - Registry function name length tag string
2019-07-24T13:26:41.014+0530 DEBUG [function-registry] - Registry function name substring tag string
2019-07-24T13:26:41.014+0530 DEBUG [flogo] - Registering legacy activity: git.tibco.com/git/product/ipaas/wi-contrib.git/contributions/General/activity/log
2019-07-24T13:26:41.014+0530 DEBUG [flogo] - Registering activity: fileuploadActivity
2019-07-24T13:26:41.014+0530 DEBUG [flogo] - Registering activity: github.com/project-flogo/contrib/activity/actreturn
2019-07-24T13:26:41.014+0530 DEBUG [flogo] - Registering trigger: github.com/project-flogo/contrib/trigger/rest
2019-07-24T13:26:41.014+0530 DEBUG [function-registry] - Registry function name isDefined tag
2019-07-24T13:26:41.014+0530 DEBUG [flogo] - Loading all plugins taken [2.75µs]
TIBCO Flogo® Runtime - 2.6.1 (Powered by Project Flogo™ - v0.9.2)
TIBCO Flogo® connector for General - 1.1.0.175
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Starting TIBCO Flogo® Runtime
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2019-07-24T13:30:58.529+0530 DEBUG [flogo.engine] - Using 'POOLED' Action Runner
2019-07-24T13:30:58.529+0530 DEBUG [flogo] - Registering type alias 'flow' for action [github.com/project-flogo/flow]
2019-07-24T13:30:58.529+0530 DEBUG [flogo] - Registering type alias 'log' for activity [git.tibco.com/git/product/ipaas/wi-contrib.git/contributions/General/activity/log]
2019-07-24T13:30:58.529+0530 DEBUG [flogo] - Registering type alias 'fileuploadActivity' for activity [fileuploadActivity]
2019-07-24T13:30:58.529+0530 DEBUG [flogo] - Registering type alias 'actreturn' for activity [github.com/project-flogo/contrib/activity/actreturn]
2019-07-24T13:30:58.529+0530 DEBUG [flogo] - Registering type alias 'rest' for trigger [github.com/project-flogo/contrib/trigger/rest]
2019-07-24T13:30:58.530+0530 DEBUG [flogo.activity.actreturn] - Mappings: map[code:200 data:map[mapping:map[myFile:=$activity[FileuploadActivity].anOutput]]]
2019-07-24T13:30:58.530+0530 DEBUG [flogo.trigger.rest] - Registering handler [POST: /upload]
2019-07-24T13:30:58.530+0530 DEBUG [flogo.trigger.rest] - Configured on port 9999
2019-07-24T13:30:58.530+0530 DEBUG [flogo.engine] - Creating app [ FileUpload-Yosi_01786855 ] with version [ 1.1.0 ]
2019-07-24T13:30:58.530+0530 INFO [flogo.engine] - Starting app [ FileUpload-Yosi_01786855 ] with version [ 1.1.0 ]
2019-07-24T13:30:58.530+0530 INFO [flogo.engine] - Engine Starting...
2019-07-24T13:30:58.530+0530 INFO [flogo.engine] - Starting Services...
2019-07-24T13:30:58.530+0530 DEBUG [flogo] - ActionRunner Service: Starting...
2019-07-24T13:30:58.530+0530 DEBUG [flogo] - Starting worker with id '1'
2019-07-24T13:30:58.530+0530 DEBUG [flogo] - Starting worker with id '2'
2019-07-24T13:30:58.530+0530 DEBUG [flogo] - Starting worker with id '3'
2019-07-24T13:30:58.530+0530 DEBUG [flogo] - Starting worker with id '4'
2019-07-24T13:30:58.530+0530 DEBUG [flogo] - Starting worker with id '5'
2019-07-24T13:30:58.530+0530 INFO [flogo] - ActionRunner Service: Started
2019-07-24T13:30:58.530+0530 INFO [flogo.engine] - Started Services
2019-07-24T13:30:58.530+0530 INFO [flogo.engine] - Starting Application...
2019-07-24T13:30:58.530+0530 INFO [flogo] - Starting Triggers...
2019-07-24T13:30:58.530+0530 DEBUG [flogo] - Trigger [ ReceiveHTTPMessage11 ]: Starting...
2019-07-24T13:30:58.531+0530 INFO [flogo] - Trigger [ ReceiveHTTPMessage11 ]: Started
2019-07-24T13:30:58.531+0530 DEBUG [flogo] - Trigger [ ReceiveHTTPMessage11 ] has ref [ github.com/project-flogo/contrib/trigger/rest ] and version [ ]
2019-07-24T13:30:58.531+0530 INFO [flogo] - Triggers Started
2019-07-24T13:30:58.531+0530 INFO [flogo.engine] - Application Started
2019-07-24T13:30:58.531+0530 INFO [flogo.engine] - Engine Started
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Runtime started in 1.943887ms
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2019-07-24T13:30:58.531+0530 INFO [flogo] - Listening on http://0.0.0.0:9999
Issue/Introduction
The debug logs are essential when you are facing the issues at runtime. To identify & verify the details of the activity and its input/output, debug logs plays an important role.
Was this article helpful?
thumb_up
Yes
thumb_down
No