Have you tried adding this to your jiveclientconfiguration.json:
I'll have to go back and check if this will log incoming requests from routes that you add yourself, but it might. If not, it can certainly serve as a pattern of how to instrument this yourself.
Hi Mark Weitzel,
Not sure if this is correct for my case(or may be I misunderstood jive app logging).
Here's an example of what I am trying to do.
Lets say I have two simple buttons on the app.
The other button has more simpler logic, say it just does 2+2, period.
Usually all i do on client side is a console.log which logs everything in a browser.
In this case, do i have a special way to call some logger method (instead of console.log) and send the logs to node.js server?
Or is the only way to have a node,js end point (independent of jive-sdk) and make ajax calls to log all such client actions ?
Your latter suggestion makes the most sense to me. In order for your node.js server to log the event, it must be notified in some capacity, so if the service you are calling is not on your node.js server, then you'll need to make that call some where in the execution order.