﻿<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>LogViewPlus Support » LogViewPlus Support » News &amp; Announcements  » LogViewPlus 3.0</title><generator>InstantForum 2017-1 Final</generator><description>LogViewPlus Support</description><link>https://www.logviewplus.com/forum/</link><webMaster>LogViewPlus Support</webMaster><lastBuildDate>Sat, 13 Jun 2026 17:02:26 GMT</lastBuildDate><ttl>20</ttl><item><title>LogViewPlus 3.0</title><link>https://www.logviewplus.com/forum/post/1559</link><description>LogViewPlus 3.0 is here!&amp;nbsp; Now with &lt;a href="https://www.logviewplus.com/docs/create_a_custom_report.html" id="if_insertedNode_1669018365739"&gt;SQL reporting and custom dashboards&lt;/a&gt;.&amp;nbsp;&amp;nbsp;We've been working on this release for over 18 months so it's really exciting to finally get it out the door and start gathering feedback.&lt;br/&gt;&lt;br/&gt;Ever since we released version 1.0, we wanted the ability to go deeper into our logs.&amp;nbsp; The classic use case became graphing CPU and memory from parsed log entries.&amp;nbsp; Not because that is particularly helpful in itself (there are better ways to track machine metrics), but because this was a great example of the kind of reporting we wanted to do.&amp;nbsp; It seems log files offer an infinite number of ad-hoc reporting scenarios.&lt;br/&gt;&lt;br/&gt;The problem wasn't parsing the data or graphing it.&amp;nbsp; The problem we had was transforming it.&amp;nbsp; Often before you can report on data you need to clean it up, transform, or aggregate it.&amp;nbsp; How can we manipulate the data to get it into the right format?&amp;nbsp; We scratched our heads on this one for a while.&amp;nbsp; We even considered building our own spreadsheet - which would have been a nightmare!&amp;nbsp; &lt;span id="if_insertedNode_1669018654636"&gt;:)&lt;/span&gt;&amp;nbsp; Fortunately, we realized the answer was staring us right in the face - SQL.&amp;nbsp; &lt;br/&gt;&lt;br/&gt;Structure Query Language was designed to solve exactly this problem.&amp;nbsp; Querying and transforming large sets of data for the purpose of reporting.&amp;nbsp; It was designed to be simple so that non-technical users can use it - and they have.&amp;nbsp; SQL is probably the single most popular computer language, so some of the learning curve could be assumed.&amp;nbsp; &lt;br/&gt;&lt;br/&gt;SQL just made sense.&amp;nbsp; Once we had this piece of the puzzle, everything else just clicked.&lt;br/&gt;&lt;br/&gt;&lt;a href="https://www.logviewplus.com/docs/lvp_sql.html" id="if_insertedNode_1669018746545"&gt;Combining SQL with log files&lt;/a&gt; is radically new.&amp;nbsp; We expect some users will look at this with a bit of confusion.&amp;nbsp; Why do you need this?&amp;nbsp; This is a new capability and it is going to take time for users to understand the kinds of problems that can now be solved.&amp;nbsp; There is a lot to be gained by making problems so easy to solve that you can do in seconds what used to take days.&amp;nbsp; It opens a lot of possibilities, but it takes time to understand that those doors are now open.&lt;br/&gt;&lt;br/&gt;There is still more work to do.&amp;nbsp; In a sense LogViewPlus 3.0 is still 1.0 for SQL and dashboard reports.&amp;nbsp; But we needed to get this release out because there is a ton of other great features that we have been sitting on like improved Windows Event Log access and a new data indicator.&amp;nbsp; It's also been 6 months since our last release, so it's time to get back into our usual 2-3 month release cycle.&lt;br/&gt;&lt;br/&gt;&lt;strong&gt;Breaking Changes&lt;/strong&gt;&lt;br/&gt;&lt;br/&gt;This release will break &lt;a href="https://www.logviewplus.com/docs/custom_readers.html" id="if_insertedNode_1669019126068"&gt;custom log readers&lt;/a&gt;.&amp;nbsp; We have had to change the ILogReader interface to support some ideas that we have on improving memory management.&amp;nbsp; We added a new ILogMem reference which needs to be used when creating new log entries.&amp;nbsp; Making the code change should be straight-forward, but we understand the work involved with communicating and redeploying within an organization.&amp;nbsp; Apologies for the inconvenience.&lt;br/&gt;&lt;br/&gt;&lt;strong&gt;What's Next?&lt;/strong&gt;&lt;br/&gt;&lt;br/&gt;LogViewPlus v3 releases will continue to improve on our new SQL reporting capability in much the same way that v2 releases improved connectivity.&amp;nbsp; Before the second half of 2023, we want LogViewPlus to have built in reporting capability for web logs, Java GC logs, and Windows security logs.&amp;nbsp; We are actively looking for more ideas.&amp;nbsp; Do you know of a widely used logging format which could benefit from a pre-built report?&amp;nbsp; &lt;a href="https://www.logviewplus.com/forum/" id="if_insertedNode_1669019668202"&gt;Let us know&lt;/a&gt;&amp;nbsp;- we would really appreciate your insight.&lt;br/&gt;&lt;br/&gt;In the next release, we want to take a look at memory usage.&amp;nbsp; LogViewPlus has always been a memory intensive application, but we have some ideas on how this can be improved.&amp;nbsp; We are going to experiment a bit and hopefully the next release will have an improved memory footprint.&lt;br/&gt;&lt;br/&gt;Now that the 3.0 release is out, we also want to focus more on quality issues such as improved performance and 4K monitor support (high DPI).&lt;br/&gt;&lt;br/&gt;That's it for now. &lt;a href="https://www.logviewplus.com/download.html" id="if_insertedNode_1669020055927"&gt;Check out the latest release&lt;/a&gt; and let us know what you think!&lt;br/&gt;&lt;br/&gt;Toby</description><pubDate>Mon, 21 Nov 2022 08:57:28 GMT</pubDate><dc:creator>LogViewPlus Support</dc:creator></item></channel></rss>