xiaohe27/logreader

The log reader which can read log files

logreader's Issues

Write Monpoly style formulas in RVM using raw logic plugin

Whenever a formula is expressed successfully, report it to Grigore

monpoly supports two consecutive event names!

Monitor

Define a method for checking whether an event is in formula or not

gen classic test case for customized log reader

provide two methods for parsing event args

If the event is monitored in the formula, then use eager evaluation and directly parse it;
Else, just ensures the args conform to the very basic syntax, and no type checking is performed at all!

Event name must appear in the sig file, though.

E.G. A (x:int) is in the sig file, but event A not occurs in the formula file.
Then in the log file, A(), A(5), A(2,3), A(hi, my)... are all accepted by Monpoly.

Test the behavior of mappedbytebuffer when reading 0 byte

ditto

exp

many invocations of StringBuilder.append VS new String(byte[]) . Test perf

Try this using Monpoly

[] forall ?user. ?db. ?p. ?data. insert (?user, ?db, ?p, ?data) => (<> fool(?a, ?b, ?c, ?d) /\ (?a = ?user /\ ?b = ?db /\ ?c = ?p /\ ?d = ?data))

Try a large log file

use rv-monitor to test single violation of publish before approve

insert a single entry that violates the pub-approve property

Check the ltl plugin of RVM

Whether there is a way to express the happens before (not transit states easily)

different outputs for violations in the property insert to db2

my log analyzer only report one third?

Is RVM only support 128 monitors?

Seems that it will report violations after 128 instances are generated anyway

strategy for log-reader generator

if the rvm spec does not contain expected formula, then it implies that the property is a simple propositional formula and no rvm methods are needed. In this case, just gen the log reader's monitor method from the simple condition derived from the simple formula, and no RVM thing is needed.

If the expected formula has been specified, then gen the log reader as normal

Liveness property

We cannot decide whether a liveness property (<> p) is violated until the end of the log has been reached. Idea: report it as non-monitorable at the beginning.

try a new approach of parsing int

each time a digit is encountered, multiply the cur number by 10 and then add the digit to the number...
Compare the perf with cur approach

use maven to build the proj

Transform normal rvm spec to rvm_m

In rvm_m spec, a boolean field "hasViolation" is inserted so that when the violation is detected, that field will be set to true.

process all the violations in a log entry at one time

exp on monpoly

if two events with diff name but same args violate two properties respectively, whether Monpoly will output the event name or not?
Currently if only one kind of event in the formula, then the event name will be omitted.

Idea about the MFOTL

Can reduce the mfotl formula to a normal temporal logic with some constraints w.r.t. time stamps. Keep a separate data structures for monitoring all the timed events. If an expected future event does not happen in the given time bound, then report violation of property.

test rvm's perf

invoke rvm's methods for every sigle event, without any monitoring.
Just increment the counter

extract a refill method

compare its perf with cur inline setting

Do an interesting experiment to Monpoly

It seems that during the parsing stage, Monpoly does not construct any object of specific data type; instead, only certain delimiters are identified and used to isolate different fields. So, test whether some not well-formed fields can be detected if there is no formula associated with it.

a test for happensBefore

a publish event and approve event happens at the same time point.
Test whether Monpoly and Log Analyzer can get the same result

Test performance improvement of inlining getStringFromBytes

Make it faster

Use totally lazy eval, and weak type checking like Monpoly.
Only detect and parse ts, event name for every event,
for the events which are not of our interests, do NOT parse it at all.

optimize method invocation!

string in Monpoly

It is interchangeable to add a pair of " to enclose string field.
There is no difference!

config file specifying for each event, which cols to display in the output of violations

Log Reader generator read the spec and hard-coded the info to the customized log reader

test perf of output to std out and then redirect to file

compare it with Monpoly's time

Add test cases for LogReader generator

Given different rvm spec, some of which are faulty, test whether the log reader generator can handle different situations well

test the time to output huge amount of data to file

add the support of comments

add the support of comments to the syntax of log

Test multiple specs in a single file

Embed the method info inside specialized log reader

So the log reader only need to have the path 2 the log file and monitoring lib in order to do the monitoring

remove objects

avoid using objects as much as possible.
record the starting and ending index of fields, construct objects when necessary.
It is not always needed to construct objects from the bytes though

make it a proj in RV family!

input: rvm spec

output: log reader which will trigger event methods for the corresponding events

Problem: how to tell whether an event is of our interest?
In Monpoly's setting, if it occurs in sig, then it is allowed to appear in the log file.
However, only if an event name appears in the formula file, will it be monitored!

If all the events are simply listed in the .rvm file, there is no way to distinguish them.