LIVE mode logging at levels below SEVERE?

244 views
Skip to first unread message

tom....@mycit.ie

unread,
Feb 22, 2016, 12:18:21 PM2/22/16
to Fujitsu RunMyProcess Developer Community
From the API docs at
http://docs.runmyprocess.com/API_Reference/FM/Request.html#P_log

-------
P_log(level, message) → {string}
Log a message.

Logs in the P_message variable of the request and in the Mongo data of the customer. In TEST mode all the levels are logged but in LIVE mode, only SEVERE level is logged. This rule is skipped if the attributes P_log is present in the resource, in this case, the given P_log will be the reference.
-------

In LIVE mode, how do I ensure that logs at levels below SEVERE are recorded?
I don't follow the part that says 'This rule is skipped if the attributes P_log is present in the resource'.

tom....@mycit.ie

unread,
Feb 25, 2016, 5:44:28 AM2/25/16
to Fujitsu RunMyProcess Developer Community, tom....@mycit.ie
I've tried adding an attribute &P_log=INFO to the web interface URL, but this causes a new unexpected problem - the presence of a scalar attribute called P_log in the request causes the P_log() function to become inaccessible in the Composite API code that uses it.

Expected method. P_log evaluated instead to freemarker.template.SimpleScalar on line 9, column 3

So the question is - where should the P_log attribute referred to in the docs be defined, to allow INFO level logging in LIVE mode?

tom....@mycit.ie

unread,
Mar 9, 2016, 11:16:41 AM3/9/16
to Fujitsu RunMyProcess Developer Community, tom....@mycit.ie
The official documentation at:
http://docs.runmyprocess.com/API_Reference/FM/Request.html#P_log
says that only SEVERE level logging is recorded in LIVE mode, unless 'the attributes(sic) P_log is present in the resource, in this case, the given P_log will be the reference'.

How does one make an attribute P_log be present in 'the resource' - what resource is being referred to here?

Reply all
Reply to author
Forward
0 new messages