We are working with many parser and different logfiles. With each new software / software release the configuration does increase.
For the moment it is required that a person does create a configuration template and shares this with the colleagues. The colleagues have to manually import the configuration into LogViewPlus.
This process works fine but requires manual work.

Improvement idea:
Within the LogViewPlus configuration it is possible to define a SMB share path for the configuration.
When you start LogViewPlus and the path for the SMB configuration is defined then LogViewPlus will automatically import the latest available configuration. In case the SMB path is not available then the last imported configuration will be used.

In the LogViewPlus configuration there should also be a simple tick-box like "Config Editor". Per default this box is not ticked.
If the box is ticked you are allowed to overwrite the config on the SMB share.
If the box is not ticket you get a message that you are not allowed to write the config to the SMB.

Maybe there is a chance to have a global SMB config + local config possible. This gives each user the chance to make use of the department wide configuration but also create a config on his own.

Best regards,
Matthias

Hi Toby,

thanks a lot for your feedback. I've spoken to my colleagues and we agree that this is a good way to start. :-)
It is a good idea to handle all points in this discussion.

If I understand your point correctly then you want to store the documentation in e.g. a word file which can be opened by the application. I was more thinking about an integration in the LogViewPlus.

Please see my example in the picture which I hope makes it better understandable.


Within a new column in LogViewPlus information from a LogViewPlus knowledgebase can be shown. In case that you do not want to show the information just hide the column.
The message can be displayed based on trigger e.g.
- parser = serverlog
- message contains "Trying to access web file."

This means for normal user the column is simply not available/ shown and therefore the software keeps easy. If you want to use the functionality then you can enable the column and feed it with information.
The knowledge base should be available for the team but I can imagine that it can also be very useful for standalone versions.

What do you think?

Best regards,
Matthias

Thanks Matthias,

Yes - I was thinking that documentation could be stored in the folder with the templates, but not necessarily opened by LogViewPlus.  LogViewPlus would just ignore anything in the directory which is not a template.

I like your documentation idea and I can see where it would be helpful.  Yesterday, we spoke briefly about Triggers.  As you indicated, the feature you outlined above could be implemented as a Trigger, but I think the action should be to add a bookmark with a note.  The advantage of this approach is that it is a bit more widely applicable to other users, and it also has built in navigation to find interesting / noteworthy parts of the log file.

...of course, LogViewPlus doesn't actually support Triggers yet.  :-)  I will prioritize this work.  Maybe we can have something for the next release.

Hope that helps,

Toby