Exporting To Xml; Using Xml Required And Optional Format-Specific Filters; Viewing Xml Format Output; Exporting To Csv - Juniper NETWORK AND SECURITY MANAGER 2010.4 - ADMININISTRATION GUIDE REV1 Administration Manual

CSV
--file-path
--include-header
Copyright © 2010, Juniper Networks, Inc.
Using Format-Specific Filters
To control how log records are exported, use format-specific filters. Some formats have
required and optional format-specific filters. Use format-specific filters after the specified
action.
NOTE: To see all format-specific filters for a format, type:
sh devSvrCli.sh --log2action --action -- format

Exporting to XML

The xml action directs the system to output logs using the XML format. To export:
Login to the Device Server as root, then change to the utility directory by typing: cd
1.
/usr/netscreen/DevSvr/utils.
To export to a file, type:
2.
sh devSvrCli.sh --log2action --action --xml <file-path> <include-header>
The Device Server exports all log records to XML; each log record becomes an XML record,
which you can open in most Web browsers.

Using XML Required and Optional Format-Specific Filters

You can use the following required and optional format-specific filters for exporting to
XML:
Multiple
No
No

Viewing XML Format Output

To view the XML schema file, type:
/usr/netscreen/DevSvr/lib/logActions/log.xsd
To export predefined and custom attack category log records to an XML file located in
the directory of the Device Server, use the --category common filter to specify the
/usr
categories:
sh devSvrCli.sh --log2action --category predefined --action --xml --file-path
/usr/MyXmlLogRecords/attacks.xml

Exporting to CSV

The csv action directs the system to output logs using the CSV format. To export:
Required Meaning
Yes Specifies where the system should
direct the output. For example,
myLogs.xml
No Specifies that the system should print
the field name before each field.
Chapter 19: Logging
803