How to introduce timestamp in chat and cobrowse console output
Hi there, We want timestamp in Chat and CoBrowse console output for automation of log monitoring.
Can you please tell us how to get this done? We are using forever to manage the application. We have tried forever configuration to introduce the timestamp, but it does not work. So we wanted it from Chat/CoBrowse console output itself.
Pegasystems Inc.
IN
The Co-browse product prints timestamps in in its logserver. It is not available in the Chat product. We will look at introducing similar capability in the the future.
Console logs are present at multiple places in the product based on the requirements and it is not possible to introduce timestamp everywhere. If you need timestamps, by applying a strategy that best suits your setup, the console.log function can be overridden in node.js to prepend a timestamp to anything that console.log prints out.
Accenture
AU
Hi, I understand logserver in cobrowse is used only for recording server which we do not have. We are expecting timestamp in console output of application.
If Pega is looking at introducing timestamp for both chat and cobrowse console output in future, can you please provide us the enhancement tracking number?
To configure timestamp by making changes to node.js, is it possible to share us more details on it? Where can we find the console.log function and what parameter has to be changed?
Thanks,
Sreethi
Accepted Solution
Infosys
AU
Hi Sreethi,
Are you looking at a timestamp in logs?
If so, you can get this done by installing log-timestamp module using npm install -g log-timestamp.
Update you app.js with this line "var logtimestamp = require('log-timestamp');"
Output in the logs will be as below.
2017-10-25 12:12:17.936 639214880 - generated session code
2017-10-25 12:12:17.945 639214880 - customer joins channel and send session code back
2017-10-25 12:12:17.945 639214880 - partnerSessionID is null
2017-10-25 12:12:17.945 socket with id 171291771139068918 joins channel "/639214880"
2017-10-25 12:12:17.945 # of sockets in room "/639214880" after joining: 1
2017-10-25 12:12:17.945 639214880 - event name : sendChannelId; emitting
2017-10-25 12:12:17.946 639214880 - event name : sendChannelId; normal emit (not broadcasting)
This works for chat and cobrowse.
Accenture
AU
Its working. Thank you :)