1
<?xml version="1.0" encoding="latin1" ?>
2
<!DOCTYPE chapter SYSTEM "chapter.dtd">
7
<year>2004</year><year>2009</year>
8
<holder>Ericsson AB. All Rights Reserved.</holder>
11
The contents of this file are subject to the Erlang Public License,
12
Version 1.1, (the "License"); you may not use this file except in
13
compliance with the License. You should have received a copy of the
14
Erlang Public License along with this software. If not, it can be
15
retrieved online at http://www.erlang.org/.
17
Software distributed under the License is distributed on an "AS IS"
18
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
19
the License for the specific language governing rights and limitations
24
<title>Audit Trail Log</title>
26
<responsible></responsible>
32
<file>snmp_audit_trail_log.xml</file>
34
<p>The chapter <em>Audit Trail Log</em> describes the audit trail logging.
36
<p>Both the agent and the manager can be configured to log
37
incoming and outgoing messages. It uses the Erlang standard log
38
mechanism <c>disk_log</c> for logging. The size and location of
39
the log files are configurable. A wrap log is used, which means
40
that when the log has grown to a maximum size, it starts from the
41
beginning of the log, overwriting existing log records.
43
<p>The log can be either a <c>read</c>, <c>write</c> or a
48
<title>Agent Logging</title>
49
<p>For the agent, a <c>write</c>, means that all <c>set</c>
50
requests and their responses are stored. No <c>get</c> requests
51
or traps are stored in a <c>write</c>. A <c>read_write</c>,
52
all requests, responses and traps are stored.
54
<p>The log uses a raw data format (basically the BER encoded
55
message), in order to minimize the CPU load needed for the log
56
mechanism. This means that the log is not human readable, but
57
needs to be formatted off-line before it can be read. Use the
59
<seealso marker="snmpa#log_to_txt">snmpa:log_to_txt</seealso>
65
<title>Manager Logging</title>
66
<p>For the manager, a <c>write</c>, means that all
67
requests (<c>set</c> and <c>get</c>) and their responses are stored.
68
No traps are stored in a <c>write</c>. A <c>read_write</c>,
69
all requests, responses and traps are stored.
71
<p>The log uses a raw data format (basically the BER encoded
72
message), in order to minimize the CPU load needed for the log
73
mechanism. This means that the log is not human readable, but
74
needs to be formatted off-line before it can be read. Use the
76
<seealso marker="snmpm#log_to_txt">snmpm:log_to_txt</seealso>