How to change the Admin Password when it is lost?

Sometimes it happens, that you might loose a password. You simply forget it or cannot find that piece of paper where you wrote it down. That is a pretty pesky situation. But what should you do in a case like this? Often software has a recovery mechanism where you have to answer specific questions. Or you have to contact the support team of a website to make them help you. But what is your chances if this happens with your LogAnalyzer password? Continue reading "How to change the Admin Password when it is lost?"

Using the reports module

The reports module is new with version 3 of LogAnalyzer. It supports HTML and PDF output and can be fully parameterized. For example, Adiscon LogAnalyzer can be used to analyze user account logons over a specific time frame, system and network errors can be identified or a status report of the whole network be generated. And at it bests: once configured, reports can be sent automatically by email in a daily, weekly or custom interval. Continue reading "Using the reports module"

What are Message Parsers?

Adiscon LogAnalyzer has a module structure and can be extended by so-called plugins. One type of plugin is the message parser. Message parsers are used to obtain structured information from a log message.

A prominent example are Windows event log messages. There is no standard format on how these look when converted to syslog. Consequently, Adiscon LogAnalyzer can not nicely display them per se. However, with the help of the Windows Event log message parser, a core component, the contents of the syslog message can be split into the relevant fields, like event id, priority, description, parameters and so on. This enables to process Windows events in syslog messages in the same way as if they were originally stored inside the database. Adiscon LogAnalyzer includes a Windows event parser suitable for use with Adiscon EventReporter and MonitorWare Agent.

Continue reading "What are Message Parsers?"

phpLogCon becomes Adiscon LogAnalyzer

As in all things, there is a certain fashion in open source project names as well. For a long time, "php*" was a great name for php-based open source solutions. However, nowadays these somewhat bulky names have been replaced by "more streamlined" names.

I personally think that dropping the "php" part makes it somewhat easier to speak and write about these projects. So we decided it was right to drop "php" from "phpLogCon". But was "LogCon" the ultimate name for a tool to search, analyze and (starting with v3) report on network event logs? A quick discussion within our group as well as with some external buddies turned out that "LogCon" is probably pretty meaningless. Even if one deciphers "Con" for "Console" – what does it mean to be a "Console" in this context? Not an easy to answer question. Bottom line: "LogCon" is pretty meaningless.

So we thought we do "the right thing" and rename the project before it becomes even more widely spread. The later you do a name change, the more painful it is. That made us think about good names. We ended up with "LogAnalyzer", because analysis is the dominant use case for this tool (especially if you think of reports as being part of the analysis ;)). Another quick search made us aware that there are (of course) lots of "LogAnalyzers". And, of course as well, all second level domains were taken.

Bare of an expensive legal adviser, we made the decision to boldly name the project "Adiscon LogAnalyzer", aka. "the log analyzer (primarily) written by Adiscon". With that approach we use our company name (which obviously legally belongs to us) together with the generic term "LogAnalyzer". That is done in the hope that it will resolve any legal friction that otherwise may occur. For the very same reason you will see us consistently referring to "Adiscon LogAnalyzer".

Continue reading "phpLogCon becomes Adiscon LogAnalyzer"