--stats and related options of
Stats will be dumped with SIGUSR2 if
--stats=PATH specified. Or, in client side,
norikra-client admin stats can export stats json data.
To fetch query output, we have 3 options:
norikra-client event fetch)
norikra-client event see)
norikra-client event sweep)
We can fetch many output events from many related queries (per service, per customers, ...) from norikra server by
sweep. Query group name is used for this purpose.
Norikra connects query outputs into other target input by specifying query group as
Once you registered a query with loopback query group, norikra does:
target_name if it is not opened yet
1. register the query
1. define fields of
target_name by outputs of the query
Loopback query group is supported on Norikra v1.0.0 or later.
STDOUT() query group to dump query output events on Console directly.
Norikra has a feature named as Listener, to accept output records of queries and to execute any processing for these events. In fact, both of
STDOUT() are implemented as built-in Listener plugins.
All Listener plugins have its name and just 1 String argument. There are used in query group fields, like
Users of Norikra can write any other Listener plugins for their own purposes. See documents of
norikra-listener-mock repository, and try it.