Nikolai Kondrashov

This is better done with the help of #91.

Hi @theblazehen, this perhaps would be good to do. Could you perhaps describe your use case, what kind of setup do you have in mind? Thank you.

Ah, I see. Yes that would be useful. However, what are you going to do with other logs? Don't you need them in Elasticsearch? Or are you just focusing on...

Alright, I understand. We'll have to consider this, thank you.

I can see that although the original "message" has all the fields, the parsed data under "_source" is missing the "in_txt" field for some reason. That field is required by...

Can you persuade Graylog to add it regardless?

Sorry, I'm a bit rusty on Elasticsearch, but can you work this around by creating an Elasticsearch mapping before starting logging? We have one in `doc/mapping.json`.

I see. Thank you for trying this out. Looks like tlog might need to handle the missing fields when reading from Elasticsearch.

@fossxplorer, at the moment input playback is not supported on the terminal. That will likely require embedding a terminal emulator into tlog-play, which we have in plans, but haven't worked...

Yes, by Web UI I mean our current Cockpit UI. However, it is planned to be a separate, reusable component, that's why I'm insisting on calling it just "Web UI...