Table of Contents | ||||||
---|---|---|---|---|---|---|
|
...
The tags beginning with web.iis
identify events generated by the IBM InfoSphere Internet Information Server Services belonging to IBM Microsoft.
Valid tags and data tables
The full tag must have at least 3 levels. The first two are fixed as web.apacheiis
. The third level identifies the type of events sent and the rest of them indicate the event subtypes.
These are the valid tags and corresponding data tables that will receive the parsers' data:
Product/Service | Tag | Data table |
---|---|---|
Apache HTTP Server Project |
|
|
|
| |
| ||
|
| |
|
For more information, read the article about Devo tags.
...
web.iis.accessNcsa
Field | Type | Source field name | Extra fields |
---|---|---|---|
eventdate |
|
| |
environment |
| venv | |
site |
| vsite | |
clon |
| vclon | |
serverdate |
|
| |
srcIp |
|
| |
user |
|
| |
method |
|
| |
url |
|
| |
protocol |
|
| |
statusCode |
|
| |
responseLength |
|
| |
srcIdentd |
|
| |
hostchain |
|
| ✓ |
tag |
|
| ✓ |
rawMessage |
|
| ✓ |
web.iis.accessW3c
Field | Type | Source field name | Extra fields |
---|---|---|---|
eventdate |
|
| |
environment |
| venv | |
site |
| vsite | |
clon |
| vclon | |
rawMessage |
|
| ✓ |
serverdate |
|
| |
srcIp |
|
| |
dstIp |
|
| |
serverPort |
|
| |
user |
|
| |
method |
|
| |
url |
|
| |
urlQuery |
|
| |
userAgent |
|
| |
referrer |
|
| |
statusCode |
|
| |
subStatus |
|
| |
win32Status |
|
| |
responseTime |
|
| |
other |
|
| |
comment |
|
| |
hostchain |
|
| ✓ |
tag |
|
| ✓ |
web.iis.accessW3cAll
Field | Type | Source field name | Extra fields |
---|---|---|---|
eventdate |
|
| |
environment |
| venv | |
site |
| vsite | |
clon |
| vclon | |
siteName |
|
| |
computerName |
|
| |
serverdate |
|
| |
srcIp |
|
| |
dstIp |
|
| |
serverName |
|
| |
serverPort |
|
| |
user |
|
| |
method |
|
| |
url |
|
| |
urlQuery |
|
| |
protocol |
|
| |
statusCode |
|
| |
referer |
|
| |
userAgent |
|
| |
cookies |
|
| |
subStatus |
|
| |
win32Status |
|
| |
responseLength |
|
| |
requestLength |
|
| |
responseTime |
|
| |
serverdate_str |
|
| |
rawMessage |
| rawSource | |
hostchain |
|
| ✓ |
tag |
|
| ✓ |
How is the data sent to Devo?
Devo recommends using the File Fetcher of the Endpoint Agent to forward IIS to Devo. In both cases:
Make sure the logs are written in text files.
Have the complete paths to the log files on hand when setting up the sending.