|Re: parse, check and count [message #1719724 is a reply to message #1719711]
||Mon, 11 January 2016 17:22
| Alexandre Montplaisir
Registered: October 2012
I would suggest that your custom parser (that is, the "trace reader" part) reproduces as closely as possible what is found in your log file. That means 1 line/event per message.
What you are trying to do then fits more into the concept of "analysis", which means taking base trace events and aggregating them or constructing some sort of state machine out of it.
In your case it would be relatively simple, you could use the XML API to define a small state system that will track the number of currently ongoing connections.
You can take a look at the documentation here:
as well as an example here (mostly the "Step 2" in your case):
The example in particular shows something very similar to your use case, except it tracks the state of individual connections, then builds a view for it. In your case, you could just have 1 state representing "the number of ongoing connections", then use the view "State System Explorer" to display the value at any given timestamp. This view is usually more for debugging purposes, but for very simple state systems it might be sufficient.
Hope this helps, let us know if you hit any problems.
Powered by FUDForum
. Page generated in 0.01649 seconds