eCatcher Log Files

Good Afternoon,
We use Splunk as a data collection/analysis tool and I would be interested in ingesting eCatcher logs…specifically individual eWon Online/Offline Status Changes as well as user initiated connections. I did a little digging around but wasn’t able to identify where these logs would be stored.

Do log files exist natively somewhere in the file structure? …Or are they only generated when you click on the ‘Logs’ button? If they do exist, where would I be able to find them?



The ewon logs are retrieved from the talk2m server and are not a local file you can access. You could poll the m2web api to get ewon status and create your own log file. This would only allow you to get the ewon online status not who is logged in. The getewons call will retrieve all ewon status and could be used to retrieve the status.

To get the users you could modify the jquery here to make the request via m2web.
You should be able to create the same file on the ewon and use the same Ajax call but update the URL to use the m2web API. See section 5.3 of the m2web reference guide. Again this would have to be periodically polled to check for connected users.


Thanks Deryck,
My goal is to analyze Online/Offline status changes to help identify anomalies in the Flexy’s connection to Talk2M servers (Ie, identify a Flexy that has become unstable and is connecting/disconnecting multiple times per day). Too often we only find out that a connection has been compromised when a customer is in need of assistance instead of being able to proactively fix connection issues. But, to accomplish this, I think I will need a true log of actual timestamped events of when the eWon changes Online/Offline state. I would like a log of user connections, so we can easily see whether or not our customers are utilizing their connection to access the system…but that’s less important.

Would it be possible to pull a log file from the eWon itself (or have the eWon push the file)?


Hello Rob,

You can pull the event logs using an Export Block Descriptor. This allows you to get the file in a few ways including emailing, and with an m2web call.

EBD: $dtEV$ftT

M2web example:$dtEV$ftT$tsU$fneventlog.txt&t2maccount=<account name>&t2musername=<Username>&t2mpassword=<T2mpassword>&t2mdeveloperid=9fdbbea1-f457-4613-bb56-0132b6c2a3a5&t2mdeviceusername=<device username>&t2mdevicepassword=<device password>