Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: CQC Events
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
Dean Roddey Wrote:I could provide another dump format.

PLEEEEEEEEEEEEEEEEEEEASE!!!!!!

Geez, what was I doing wrong all those times before when I begged for logfile changes to make it a little more manageable/readable? :tounge
I think the current log file dump is pretty readable if that is what you are doing with it. The thing a csv file does for you is to be able to treat it as structured data. This opens a lot of possibilities.
Well, I find its great verbosity to be a hindrance to my assimilating the data. Each entry takes 5 lines, only one of which contains the actual logged message I sent out. So, if all of that data contained in those 5 lines were able to be put into a single comma-delimited line, then I'd only have 1 column to scan down....my messages would be a lot lot easier to find.
I should have been clearer. A csv may provide a little better readability if the output is structred in a given order. I have the message as the 3rd column below so it works out well. If it were in the same order as what is presented in the log file it would be further back in the line. What you want is a condensed version of the log in a tab delimited format if you want better human readability. A csv would take something like this

Code:
07/12 11:20:08-CQCMS, CQCServer, CIDOrbServerListener
{
    CIDLib, CIDLib_Thread.cpp.914, API Failed/App Status
    Thread CIDOrbSrvSpoolThread_6 is still running, trying to stop it
}
07/12 11:20:14-CQCMS, CQCWebSrv, CIDOrbClientSpoolThread_4
{
    CIDOrb, CIDOrb_ClientBaseHelpers.cpp.702, API Failed/Lost Connection
    The server at 192.168.182.129:13502 has closed the connection
}
07/12 11:20:15-CQCMS, CQCWebSrv, OrbAutoRebindThread0
{
    CIDOrbUC, CIDOrbUC_AutoRebind.cpp.229, Warning/Internal
    Orb rebind thread restarted after error. See the logs
}
07/12 14:11:17-CQCMS, CQCDataSrv, CIDOrbSrvWorkThread_2
{
    CQCDataSrv, CQCDataSrv_IntfServerImpl.cpp.1116, Status/App Status
    User drawn interface 'TestOverlay' was updated on the Master Server
}
07/12 14:11:47-CQCMS, CQCDataSrv, CIDOrbSrvWorkThread_1
{
    CQCDataSrv, CQCDataSrv_IntfServerImpl.cpp.1116, Status/App Status
    User drawn interface 'TestOverlay' was updated on the Master Server
}
07/12 14:15:30-CQCMS, CQCDataSrv, CIDOrbSrvWorkThread_4
{
    CQCDataSrv, CQCDataSrv_IntfServerImpl.cpp.1116, Status/App Status
    User drawn interface 'TestOverlay' was updated on the Master Server
}
07/12 17:48:34-CQCMS, CQCDataSrv, CIDOrbSrvWorkThread_1
{
    CQCDataSrv, CQCDataSrv_IntfServerImpl.cpp.1116, Status/App Status
    User drawn interface 'TestOverlay' was updated on the Master Server
}
07/12 11:20:09-CQCMS, CQCIntfView, CIDOrbServerListener
{
    CIDLib, CIDLib_Thread.cpp.914, API Failed/App Status
    Thread CIDOrbSrvSpoolThread_5 is still running, trying to stop it
}
07/12 14:22:02-CQCMS, CQCServer, CIDOrbServerListener
{
    CIDLib, CIDLib_Thread.cpp.914, API Failed/App Status
    Thread CIDOrbSrvSpoolThread_31 is still running, trying to stop it
}

and turn it into this

Code:
"07/12 11:20:08","CQCMS","Thread CIDOrbSrvSpoolThread_6 is still running, trying to stop it",,"API Failed","App Status","CQCServer","CIDOrbServerListener"
"07/12 11:20:14","CQCMS","The server at 192.168.182.129:13502 has closed the connection",,"API Failed","Lost Connection","CQCWebSrv","CIDOrbClientSpoolThread_4"
"07/12 11:20:15","CQCMS","Orb rebind thread restarted after error. See the logs",,"Warning","Internal","CQCWebSrv","OrbAutoRebindThread0"
"07/12 14:11:17","CQCMS","User drawn interface 'TestOverlay' was updated on the Master Server",,"Status","App Status","CQCDataSrv","CIDOrbSrvWorkThread_2"
"07/12 14:11:47","CQCMS","User drawn interface 'TestOverlay' was updated on the Master Server",,"Status","App Status","CQCDataSrv","CIDOrbSrvWorkThread_1"
"07/12 14:15:30","CQCMS","User drawn interface 'TestOverlay' was updated on the Master Server",,"Status","App Status","CQCDataSrv","CIDOrbSrvWorkThread_4"
"07/12 17:48:34","CQCMS","User drawn interface 'TestOverlay' was updated on the Master Server",,"Status","App Status","CQCDataSrv","CIDOrbSrvWorkThread_1"
"07/12 11:20:09","CQCMS","Thread CIDOrbSrvSpoolThread_5 is still running, trying to stop it",,"API Failed","App Status","CQCIntfView","CIDOrbServerListener"
"07/12 14:22:02","CQCMS","Thread CIDOrbSrvSpoolThread_31 is still running, trying to stop it",,"API Failed","App Status","CQCServer","CIDOrbServerListener"

A condensed, tab delimited output would look like this

Code:
7/12/2007 11:20    CQCMS    "Thread CIDOrbSrvSpoolThread_6 is still running, trying to stop it"
7/12/2007 11:20    CQCMS    The server at 192.168.182.129:13502 has closed the connection
7/12/2007 11:20    CQCMS    Orb rebind thread restarted after error. See the logs
7/12/2007 14:11    CQCMS    User drawn interface 'TestOverlay' was updated on the Master Server
7/12/2007 14:11    CQCMS    User drawn interface 'TestOverlay' was updated on the Master Server
7/12/2007 14:15    CQCMS    User drawn interface 'TestOverlay' was updated on the Master Server
7/12/2007 17:48    CQCMS    User drawn interface 'TestOverlay' was updated on the Master Server
7/12/2007 11:20    CQCMS    "Thread CIDOrbSrvSpoolThread_5 is still running, trying to stop it"
7/12/2007 14:22    CQCMS    "Thread CIDOrbSrvSpoolThread_31 is still running, trying to stop it"
Part of the problem is that you really need all those other fields in many cases to have the information be meaningful. If you column align all those, you'd have a very wide page of info that would in itself become hard to read.
I would agree. If you did a full tab delimited dump it would be way too wide unless you are using the proverbial "10' interface". For a quick, cursory exploration of the log file a timestamp, server, and message might not be such a bad thing. Then if you see something that stands out you could go after the normal log to get all the details.
Pages: 1 2