Skip to content

Commit 95509a9

Browse files
fix(juniper_netscreen): update README.md
1 parent 632491d commit 95509a9

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

‎packages/juniper_netscreen/docs/README.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -164,6 +164,8 @@ An example event for `log` looks as following:
164164
| http.request.method | HTTP request method. The value should retain its casing from the original event. For example, `GET`, `get`, and `GeT` are all considered valid values for this field. | keyword |
165165
| http.request.referrer | Referrer for this HTTP request. | keyword |
166166
| input.type | Type of Filebeat input. | keyword |
167+
| log.file.device_id | Device Id of the log file this event came from. | keyword |
168+
| log.file.inode | Inode of the log file this event came from. | keyword |
167169
| log.file.path | Full path to the log file this event came from. | keyword |
168170
| log.flags | Flags for the log file. | keyword |
169171
| log.level | Original log level of the log event. If the source of the event provides a log level or textual severity, this is the one that goes in `log.level`. If your source doesn't specify one, you may put your event transport's severity here (e.g. Syslog severity). Some examples are `warn`, `err`, `i`, `informational`. | keyword |

0 commit comments

Comments
 (0)