Is your feature request related to a problem? Please describe.
Currently AnaLog outputs the log into the console as a continuous stream of lines independent from events like watching start/stop, log rotation, (dis)appearing, etc. It makes the output misleading in some cases, for example when a watching was manually stopped and then started back again (the output would lack a portion of records but there would be no information about it).
Describe the solution you'd like
Every time AnaLog encounters an event like mentioned above, it should emit a special sign into the console to inform the user about the event. The sign (or mark) should have a timestamp to be bound to the same timeline as ordinary records. Besides, it should have a distinct design to be easily recognized by the user as the service information.
Describe alternatives you've considered
Ordinary popup messages are also useful for that purposes but they have no time binding so that it is easy to miss them. They are considered as a complement rather than an alternative to the markers.
Additional context
This is primarily a fronted feature with less server participation.
Is your feature request related to a problem? Please describe. Currently AnaLog outputs the log into the console as a continuous stream of lines independent from events like watching start/stop, log rotation, (dis)appearing, etc. It makes the output misleading in some cases, for example when a watching was manually stopped and then started back again (the output would lack a portion of records but there would be no information about it).
Describe the solution you'd like Every time AnaLog encounters an event like mentioned above, it should emit a special sign into the console to inform the user about the event. The sign (or mark) should have a timestamp to be bound to the same timeline as ordinary records. Besides, it should have a distinct design to be easily recognized by the user as the service information.
Describe alternatives you've considered Ordinary popup messages are also useful for that purposes but they have no time binding so that it is easy to miss them. They are considered as a complement rather than an alternative to the markers.
Additional context This is primarily a fronted feature with less server participation.