You can select one or more sources to read from. A source can be one of the following:
Local directory; all files inside the directory which match the pattern (see below) are read
URL denoting a file; all supported protocols are possible, e.g
(if you have
installed the SSH extension)
URL denoting a directory; this is only supported for
and the URL must end with
;type=d. Recursive reading of sub-directories is not supported. You must make sure that
either directory does not contain any sub directories or that you exclude any subdirectories using
the directory contents pattern. Otherwise you may get an error while reading.
When reading all files in a directory, you can specify a regular expression (not a wildcard expression!) to
which the files in the directory must match.
Now you have to select the format of the log files. First you need to specify which locale is used on the
server. This is necessary for parsing dates since e.g. the month names are different in different locales.
all log files are created with an english locale, the default is
en_US. You only need to change this if your
webserver uses a different locale when writing the log files. The next
step is to specify the date format used
in the log file. Again you only need to change this, if you are using
a non-standard date format. The format specification
identical to the one in the Apache configuration but instead uses the Java syntax. Take a look at the
The last piece is the actual format specification of a complete log line. This format is
identical to the one in the Apache configuration, i.e. you can simply copy it from there. The full syntax is
given in the
. The most commonly used fields are:
- the size of the response in bytes
- the clients IP address or name
- the value of the request header
- the remote logname, if ident is used
- the request itself
- the HTTP status code
- the request's timstamp
- the remote user, if authentication is used
- the virtual host this request was sent to
%0 - this special field can be used to process unknown fields
The input fields contains the two most commonly used format,
common and combined. If you click on Analyze log the first line of the first file is read and analyzed with the given
format. If the format matches, you will get a preview of the columns and types in the table below. The
types and columns names are hard-coded and cannot be changed.
In the second tab you can specify time ranges for requests you want to included in the output. All request
the specified range are filtered out. The start date is inclusive whereas the end date is exclusive.
to filter all request from March 2013, you would specify
as start date and
as end date. If you are using flow variables to specify dates, you must use the date format as it is used
in the log file and specified in the dialog.
A list of input files, directories, or URLs. See explanation above for details
Directory contents pattern
Pattern that files inside a directory must match in order to get processes. Note that
this is a regular expression and not a wildcard expression.
The locale used in the log files for dates
The format used for the request timestamps. For details see above.
The log file format specification. This is identical to the one used in the Apache
Split request field
If selected, the request field (%r) will be split into three columns, one
for the HTTP method (equal to %m), one for the requested URI, and one for the protocol (equal to %H).
You need to ensure, however that %m and %H are not part of the log format themselves.
The start date of the requests which should be included in the output. The start date is inclusive.
The end date of the requests which should be included in the output. The start date is exclusive.
Wait a sec! You want to explore and install nodes even faster? We highly recommend our
NodePit for KNIME
extension for your KNIME Analytics Platform.
Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well?
Do you think, the search results could be improved or something is missing?
Then please get in touch! Alternatively, you can send us an email to email@example.com,
follow @NodePit on Twitter,
or chat on Gitter!
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.