Hi all, hope all fine around there.
As in object, I was wondering if there’s a way to make a print (or using another function) to make infos collected by urs visible in TServer logs.
The goal is to have in a single file all informations about call (conn_id, absolute start time, absolute end time, extension dn and agent login who responded to a call, domain), 'cause in TServer logs I can collect a lot of infos, but very often they’re aren’t stored systemically in the files, and for a lot of infos theres isn’t a clear relation between the call and its identity (uuid, connection id, etc.).
Best regards,
Gef.
- No, unless you use attached data as “log” but…
- If you connid changes for same call you have another bigger issue. I think we discussed that before
Enviado de meu E6633 usando o Tapatalk
Hi Cav, me too does not want to use attach data too intensively. At the moment I’m joining all the info extracting them from both the tserver and urs log files; I guess I must continue to do so.
That is what you usually do as many times you have to read between lines as well on events and log snaps where connid is not a key
Enviado de meu E6633 usando o Tapatalk
Yessir, exactly. Just tried a shot to see if I could save some file handling work.
One way to go about it is to actually do what we did: create a tool that merges logs from multiple servers into one.
Simple way: use dancer’s shell (https://www.netfort.gr.jp/~dancer/software/dsh.html.en) and then
dsh -Mac – tail -f /var/log/genesys8/*.log
The -a is for all machine names that you’ve defined in ~/.dsh/machines.list
The -c is for concurrent running of tail
The -M prepends the hostname to every line of output.
We found that scanning logs in realtime or near-relatime provides us with a plethora of information otherwise inaccessible to an average Genesys admin
Look into http://logscape.net/ - the github version is amazing.