List view
This milestone is about preventing Tailviewer from becoming a monolithic application. Tailviewer shall support dynamic loading/unloading of plugins which can co-exist in different versions. A lot of newer features will be implemented as plugins as to not clutter the already big tailviewer code base. Part of this milestone is identifying possible interfaces which plugins can implement. These interfaces should allow plugins to extend various features such as the analysis feature.
No due date•1/6 issues closedThis milestone is about allowing the user to create an analysis which consists of various views onto a list of log files. Each view displays a different aspect of these log files. These analyses can be shared with others and re-used in order to more quickly analyse the same problems over and over. Examples of these views are: ### Quick Info: Display the first/last occurrence of a regex Can be used to gather quick facts about the log file being analysed. Example: Gather Processor, OS, memory, product version, etc.. ### Events: A chronological list of things which match an event (by regex) Can be used to gain an overview of important things: * Device X was found at T1 * The application restarted at T2 ### Counters: The number of log entries which match a filter * How many crashes occured? * How often did the user do X?
No due date•12/12 issues closed- No due date•0/3 issues closed
Tailviewer shall be capable of adding data sources from remote computers over a LAN/WAN (obviously networked files are already supported). This shall be enabled by installing Tailviewer on all participating machines, connecting them via SharpRemote. Filtering remote data sources shall be performed on the remote machine, obviously, while only the currently visible subset shall be streamed over the network. A remote data source is one running Tailviewer instance on another device and all of it's local data sources shall be automatically visible as children. Introduce an icon to differentiate between remote and local data sources (important when grouping different data sources) and display it next to the data source.
No due dateTailviewer shall be able to display live event tracing data - a data source would be associated with a session instead of a log file. The user shall be able to specify the list of active providers in a nice and easy way (concentrate on .NET specific provider first). Find out if, and how a session can be displayed live as well as recorded into a file using the ETW native format. The user shall also be able to simply open a previously written event log like any other data source. It should be possible to add a data source which shows the very same log messages as event viewer (by default),e.g. "Application, Security, Setup and System" data sources should be supplied as well as the custom data source described above. The view should be toggle-able between the default text-based view and a new table view that can have its columns configured (hide/show, no sorting).
No due dateCurrently the entire log file is read into memory, effectively requring double the amount of virtual memory than the file consumes on disk. This is unacceptable for files > 1Gb. Tailviewer should start streaming files into memory, only building one or more indexes as required by the current features. Memory consumption should be more or less irrelevant on the amount of files currently opened. In order to facilitate this, the current log viewer must be replaced by one which allows for a virtualized model (ditching the view model entirely), but also the relevant ILogFile implementation must be written.
No due date•1/2 issues closed- No due date•0/3 issues closed
It shall be possible to group multiple log files together so they can be viewed as one (virtual) log file.
No due date•7/12 issues closed