Volga Infras

• beginning: Start consuming from the beginning of the stream. If the topic has wrapped, i.e., started to drop chunks, the first message will be the oldest one remaining on the topic.
• end: Start consuming from the end of the stream
• unread: Start consuming from last acked message plus one

Indicates where to start consuming in the topic stream

If topic-tag is set, only messages produced with the same topic-tag will be received by this consumer. This can be useful when multiple applications need to share the same topic of infra.

Consume only messages that match this Perl RE pattern, and just skip all other messages.

Must have the value true.

Invert the match provided by the re-match pattern

A string that matches:

expr = term \*( ',' term )
term = path \*( '/' '[' expr ']' )
path = field-name [ '/' path ]
field-name = identifier / identifier '=' identifier

For example:

• fields=foo,bar - selects the fields foo and bar
• fields=foo/bar - selects the fields bar in foo
• fields=foo/[bar,baz] - selects bar and baz in foo
• fields=foo=x - selects foo, and renames foo to x in the output

Volga can trim incoming messages, delivering only the fields given here.

In follow mode, the client will continue to consume, although the last message in the topic has been delivered. By default the client will receive a socket close when the topic has been exhausted.

By default, a REST consumer will receive JSON structs, with sequence number and more. With this option, only the payload is delivered. This option is useful when viewing plain text logs.

Receive messages regardless of filters such as topic-tags and destination sites. This is sometime useful for debugging