The web interface is intuitive, and you will find a clickable question mark near many options, where you can find context–related help.If you need information about a specific option, you should look at context–related help–popups. If you need information about how to solve a specific task, this manual is the right place to look.Point your web browser to the server you installed op5 LogServer Extension on and click the icon for op5 LogServer. That will take you to the login window.To search for a message, simply type your search phrase in the search form box and press enter. You will then do a search in the full-text search index table in the database.Both the result table and the timebar are updated when each hour of data are searched through in the database. If you want to stop the search just click on ”Stop” just below the search text field.Example: search of ”connect” instead of msg=”connect” will be searched in all text fields, taking more resources from the server.If you want to define a more advanced search query you can use the op5 LogServer query language.In op5 LogServer we have created a own Query Language to be able to do more complex searches. The usage is described below.
![]()
= means ‘contains’
![]()
: means ‘starts with’
![]()
~ means ‘matches regular expression’
Example 1 Logs that have severity ”warn” or ”info”, and do not contain words ”statistics” or ”daemon” in any field, and where field ”msg” does not begin with ”Log”, and that were not generated by ”sshd”Available fields: sev, fac, event, ip, ident, host, pid, msgSeverities: emerg(ency), alert, crit(ical), err(or), warn(ing), notice, info, debugFacilities: kernel, user, mail, daemon, auth, syslog, lpr, news, uucp, cron, authpriv, ftp, ntp, logaudit, logalert, clock2, local0 to local7, markWe have also created a Query builder function to make it easy for users to build their custom filters.The Query Builder is bidirectional since op5 LogServer 3.3, meaning that it will expand your filter’s criteria to the correct boxes when selecting a filter. You can only get ”OR” function in Query Builder
![]()
To select more than one Severity or Facility, press and hold the Ctrl-key and click to select additional items.Most UNIX daemons log their messages with more than one severity -- depending on the message your database server might send a notice message or a critical message – or any of the other available messages.This is the category of data. For instance: Your mail server daemons may log only using the mail facility and you will find most log on failures in the auth facility. This field is part of the syslog specification.This is the actual log message. This is the field that is the least well defined. You may want to use this to exclude any messages that clutter your search results.
![]()
![]()
![]()
![]()
Click Save.
![]()
Enter your search criteria. You can use a simple full text search, the query language, or the query builder.
![]()
Press Search now.Since the filters are organised in a hierarchical data model (a tree-like structure) you can create multiple filters in multiple levels based on the same parent filter. Filters created from filters will become dependent on the filter out of which they were created.The user management in op5 LogServer supports making filters Global or Private (My filters) and assigning special permissions to the filters.
Note: If you want to remove a filter that has other filters based on it you must first delete the ”sub filters”. Otherwise the ”sub filters” are left unusable.To view/edit the search criteria of an existing filter, select it from the filter dropdown menu and press.
Note: A user can’t edit Global filters unless they are member of the ’Filter administrators’ group.If you are member of ‘Filter administrators’ group you can view how your filter looks like and also change/assign permission to filters.
![]()
![]()
Note: When you create/manage a filter, you need to decide which users should be able to use it. Default is none.By clicking on the Down arrow on the Search now button will allow you to set a refresh period of the page. You can set it between 30 and 300 seconds.The Auto refresh works like the UNIX program tail, showing the last x messages,The format is a | (pipe) separated list.You can move back and forth in time by using the timeline. If you go back in time and lack the data in the database you can easily import it, see Import archived data on page 14The GUI will now display the X messages, matching the search criteria within the given time. To change the number or messages displayed, see Modify view settings.Messages are by default searched from the time you selected until the last message in database.
Example 5 If you select 2012-01-09 hour 17, you will be able to search on all messages between 17:00 and the last message imported into the database.
Note: No-day-limit or unlimited search mod is deprecated, this is now the normal behavior.To move in time you click the small arrows, they will move in time and display the X previoius/following messages matching the time in the timeline.Data is kept in the database only for a limited amount of time, so that archived data does not occupy uncompressed disk space and slow down your searches.However, the archived data is not discarded until after a much longer time. It is merely compressed and archived for possible future access.When you have started an import it will continue in the background so you can continue to browse your messages.The import process will start to import the logs that correspond to your selection. A status message in the upper left corner of the GUI will display the status of the import:
![]()
A black hour number in the timeline indicate that the import is done. The date will become gray indicating that you have logs on that date.
Note: In the search result there is a column called EventID. If the log row contains a MS Windows Event, the eventid is displayed as a link directly to www.eventids.net. If you click on the link you will be sent to the page for the eventid in the log row.
![]()
Auto reports: Does scheduled searches and sends them to a list of user via e-mail, or save them in a folder on your file server.
![]()
Summary reports: Gives you top 10 hosts based on hits for each filter you have access to, and create graphs (message per minute) from global/private filters.If you wish to create an Auto report - for instance you might want a log of failed password login attempts sent to you weekly - you should start by creating the appropriate search filter. See section Search Filters on page 8 for information on how to create filters.If you have your search filter ready and wish to us it to create a report, click Reports in the top menu, and click Add new report.
![]()
Click Reports in the top menuThis is the name of the report you are creating. Choose a name that is descriptive - not only for your own sake, but also for your colleagues.
![]()
Choose path if you want the report tot be created on a file server. You need to mount the file share on your op5 LogServer server in order to have a local path. See Using Remote Storage.Enter the email addresses that should receive the report (separated with comma ‘,’), or the path in which it should be saved.Choose - Every hour, Every 6 hours, Every 12 hours, Daily, Weekly or Monthly - How often the report should be genreated.When you have created your report, it will show up every time you click Reports in the page top menu.If you wish to create a global or private summary report – for instance you might want to view the number of hits for a filter matching incorrect ssh connections – you should start by creating the appropriate search filter.
Note: When you have added your report it will take maximum 5 minutes until any graps is created.When you have created your report, it will show up every time you click Reports in the page top menu and then Global or Private summary reports flap.To view a report click on theto the right of the report.
You can “zoom” in on the grap by selecting what timeframe you want to look at by pressing the links under the graph image.
![]()
Compressed archive on remote file server for storage up to many years, only limited by the amount of disk space availableWe recommend that you use op5 Monitor to check the available disk space on all disks used to store log data, so that you receive an alert if disk space is insufficient.The picture below shows how the settings page looks like. Each option will be described in the next sections.How long you wish to keep data in the database - the Rotate database After setting - depends on how much data you log. Most organisations are happy with the default setting of 5 days, but if you log very much data you may need to store it for a shorter amount of time, regarding performance and disk space used.The Local Storage Path is a setting you normally do not need to touch, unless you wish to save it on another storage unit.The Keep archave in local storage setting with its default of 5 days regulates for how long the data will be stored in the local filesystem on the op5 LogServer machine. After this period of time, data will be stored only on the remote file server - still accessible but the access will be slower.The issue is disk space; you would normally want to save data for as long as possible, without filling up the local hard disk. Keep in mind that since the amount of logged data per day often increases over time, you need a lot of free disk space for the future.You should mount a remote file server in the file system on your LogServer machine. You can read more about this in Section B - Using Remote Storage.When you have done so, set the Remote Storage Path to the mount point - you can use /opt/logserver/remote or any other path you choose.If you wish to impose a time limit on the remote storage with the setting Keep Archive in Remote Storage.
Note: For example if you have a lot of log messages from a firewall that contains a lot of ”non-words”, binary data dumps and such.
Note: If you turn off the full text index, queries using full text syntax will still work but a bit slower.Here you can define the hostname of your op5 monitor server that will be used in the links in the host field in the search result.Check this check box to have the links in the host field in the search result pointing to the new Ninja Gui instead of the old 4.x version.If you like to have an custom URL, instead of the standard URL to Monitor for the link in the host field in the search result, you can define it here.This can be any URL and to have the hostname added to the URL just use a [host] like in this example:
Example 6 You can import already exported filters here. Just click on Browse to choose the file. Then click on Import to import the filters.Choose the filters you like to export and ”move“ them over from Available filters to Selected filters. Click on Export to save the XML file containing the filters. You can then import them via the Importfilters section in Settings.When exporting a filter that depends on an other filter both of themwill be exported to make sure dependencies are untouched.
Note: To access Users and Groups, you have to be logged on as a user with admin privileges. If you have user administrator privileges, you will see a link called Users and Groups in the main menu at the top.When logged in to the op5 LogServer you will see your username and a logout button in the top right corner.Pressing the username will popup a “Update password” dialogue.As default all new created user can see all log messages. To have it the opposite way you should remove the group all from the filter all. The you create groups for different level of users and set the permissions on the filters for the groups you created.
Create/Manage Global filters, Create/Manage Summary reports Create/Manage Auto reports, No access to Summary reports Since version 3.5 of op5 LogServer we have included audit tracking to make sure an administrator can se what the users have been doing. The following actions is logged:
Shows everyting except for audit messages. This is useful as a base for other filters, so that users don’t see audit messages.