HP t310 PCoIP Administrator's Guide - Page 109

Using the Diagnostic Tools, 6.1 Viewing and Clearing Event Log Messages, 6.1.1 Syslog Features

Get HP t310 PDF manuals and user guides View all HP t310 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 109 highlights

PCoIP Administrator's Guide 6 Using the Diagnostic Tools The Diagnostic menu contains links to pages with run-time information and functions that may be useful for troubleshooting. Note: The Diagnostic options in the OSD are a subset of those available through the Administrative Web Interface. 6.1 Viewing and Clearing Event Log Messages The Event Log page lets you view and clear event log messages from the host or client. The web interface lets you change the log filter setting on the device, which controls which messages are put in the log. When you set the filter to "terse", the device logs terse messages. The Event Log page also lets you enable and define syslog as a way of collecting and reporting your events that meets the IETF standard for logging program messages. 6.1.1 Syslog Features l Allows separation of the software that generates messages from the system that stores them and the software that reports and analyzes them. l Provides devices that would otherwise be unable to communicate a way to notify administrators of problems or performance. l Can be used for computer system management and security auditing as well as generalized informational, analysis, and debugging messages. l Is supported by a wide variety of devices and receivers across multiple platforms. l Can be used to integrate log data from many different types of systems into a central repository. l Has messages that: o refer to a facility (auth, authpriv, daemon, cron, ftp, lpr, kern, mail, news, syslog, user, uucp, local0, ... , local7 ) . o are assigned a priority/level (Emergency, Alert, Critical, Error, Warning, Notice, Info or Debug) by the sender of the message. l Lets you direct messages to various local devices (console), files (/var/log/) or remote syslog daemons. Note: Take care when you update the configuration as omitting or misdirecting message facilities or levels can cause important messages to be ignored by syslog or overlooked by the administrator. TER0606004 Issue 16 109

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
6
Using the Diagnostic Tools
The
Diagnostic
menu contains links to pages with run-time information and functions that
may be useful for troubleshooting.
Note: The Diagnostic options in the OSD are a subset of those available through the Administrative
Web Interface.
6.1
Viewing and Clearing Event Log Messages
The
Event Log
page lets you view and clear event log messages from the host or client.
The web interface lets you change the log filter setting on the device, which controls which
messages are put in the log. When you set the filter to “terse”, the device logs terse
messages.
The
Event Log
page also lets you enable and define syslog as a way of collecting and
reporting your events that meets the IETF standard for logging program messages.
6.1.1
Syslog Features
l
Allows separation of the software that generates messages from the system that stores
them and the software that reports and analyzes them.
l
Provides devices that would otherwise be unable to communicate a way to notify
administrators of problems or performance.
l
Can be used for computer system management and security auditing as well as
generalized informational, analysis, and debugging messages.
l
Is supported by a wide variety of devices and receivers across multiple platforms.
l
Can be used to integrate log data from many different types of systems into a central
repository.
l
Has messages that:
o
refer to a facility (auth, authpriv, daemon, cron, ftp, lpr, kern, mail, news, syslog,
user, uucp, local0, ... , local7 ) .
o
are assigned a priority/level (Emergency, Alert, Critical, Error, Warning, Notice,
Info or Debug) by the sender of the message.
l
Lets you direct messages to various local devices (console), files (/var/log/) or remote
syslog daemons.
Note: Take care when you update the configuration as omitting or misdirecting message
facilities or levels can cause important messages to be ignored by syslog or overlooked
by the administrator.
TER0606004 Issue 16
109
PCoIP Administrator's Guide