Dell PowerStore 3000X EMC PowerStore Service Scripts Guide - Page 73

Table 1. Journal field descriptions continued, System Journal Fields

Get Dell PowerStore 3000X PDF manuals and user guides View all Dell PowerStore 3000X manuals
Add to My Manuals
Save this manual to your list of manuals

Page 73 highlights

Table 1. Journal field descriptions (continued) Type Name Default _SELINUX_CONTEXT Default Default _SOURCE_REALTIME_TIMESTAMP _STREAM_ID Default Default Default Default Default _SYSTEMD_CGROUP, _SYSTEMD_INVOCATION_ID, _SYSTEMD_OWNER_UID, _SYSTEMD_SESSION, _SYSTEMD_SLICE, _SYSTEMD_UNIT, _SYSTEMD_USER_UNIT _TRANSPORT _UDEV_DEVLINK _UDEV_DEVNODE _UDEV_SYSNAME Default Custom Default Default Default Custom _UID AUDIT_TIMESTAMP, AUDIT_USERNAME, AUDIT_IS_SUCCESSFUL, AUDIT_CLIENT_ADDRESS, AUDIT_SERVER_ADDRESS, AUDIT_APPLIANCE_ID, AUDIT_JOB_ID, AUDIT_RESOURCE_TYPE, AUDIT_RESOURCE_ACTION, AUDIT_RESOURCE_ID, AUDIT_RESOURCE_NAME, AUDIT_MESSAGE_CODE, AUDIT_MESSAGE_L10N, AUDIT_REQUEST_BODY CODE_FILE CODE_FUNC CODE_LINE COMPONENT Custom Default Default Custom CONTEXT_ID COREDUMP_UNIT, COREDUMP_USER_UNIT ERRNO MARKER Description The SELinux security context (label) of the process from where the journal entry originates from. Earliest trusted timestamp of the message. Unique identifier of the stream connection when it was first created. Systemd information of the process the journal entry originates from. Information on how the journal service received the message entry. The low-level Unix error number causing this entry. The device node path of this device in /dev. The kernel device name as it shows up in the device tree below / sys. The user ID of the process the journal entry originates from. Additional fields used in the audit logs. Source file name that contains the code generating the message. Function name in the code generating the message. Location of the code in the source file generating the message. The logging component. Values include: • CP-Components that enable management of the cluster. • DP-Backend data engine components. • Platform-Backend platform or base storage container (BSC) components. • Service-Serviceability or service container components. • Fireman-Backend services responsible for handling communications between internal components. • PostGres-PostGres services. Unique identifier to track requests. Used to annotate messages containing coredumps from system and session units. Low-level Unix-based error number associated with the entry in the journal. Unique string used to quickly identify certain events or conditions. Values include: REST, RemoteSupport, ZMQ, NDU (nondisruptive upgrades), CC (cluster creation), LUN, System Journal Fields 73

  • 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
Table 1. Journal field descriptions (continued)
Type
Name
Description
Default
_SELINUX_CONTEXT
The SELinux security context (label) of the process from where
the journal entry originates from.
Default
_SOURCE_REALTIME_TIMESTAMP
Earliest trusted timestamp of the message.
Default
_STREAM_ID
Unique identifier of the stream connection when it was first
created.
Default
_SYSTEMD_CGROUP,
_SYSTEMD_INVOCATION_ID,
_SYSTEMD_OWNER_UID,
_SYSTEMD_SESSION, _SYSTEMD_SLICE,
_SYSTEMD_UNIT, _SYSTEMD_USER_UNIT
Systemd information of the process the journal entry originates
from.
Default
_TRANSPORT
Information on how the journal service received the message entry.
Default
_UDEV_DEVLINK
The low-level Unix error number causing this entry.
Default
_UDEV_DEVNODE
The device node path of this device in /dev.
Default
_UDEV_SYSNAME
The kernel device name as it shows up in the device tree below /
sys.
Default
_UID
The user ID of the process the journal entry originates from.
Custom
AUDIT_TIMESTAMP, AUDIT_USERNAME,
AUDIT_IS_SUCCESSFUL,
AUDIT_CLIENT_ADDRESS,
AUDIT_SERVER_ADDRESS,
AUDIT_APPLIANCE_ID, AUDIT_JOB_ID,
AUDIT_RESOURCE_TYPE,
AUDIT_RESOURCE_ACTION,
AUDIT_RESOURCE_ID,
AUDIT_RESOURCE_NAME,
AUDIT_MESSAGE_CODE,
AUDIT_MESSAGE_L10N,
AUDIT_REQUEST_BODY
Additional fields used in the audit logs.
Default
CODE_FILE
Source file name that contains the code generating the message.
Default
CODE_FUNC
Function name in the code generating the message.
Default
CODE_LINE
Location of the code in the source file generating the message.
Custom
COMPONENT
The logging component. Values include:
•
CP
—Components that enable management of the cluster.
•
DP
—Backend data engine components.
•
Platform
—Backend platform or base storage container
(BSC) components.
•
Service
—Serviceability or service container components.
•
Fireman
—Backend services responsible for handling
communications between internal components.
•
PostGres
—PostGres services.
Custom
CONTEXT_ID
Unique identifier to track requests.
Default
COREDUMP_UNIT,
COREDUMP_USER_UNIT
Used to annotate messages containing coredumps from system
and session units.
Default
ERRNO
Low-level Unix-based error number associated with the entry in
the journal.
Custom
MARKER
Unique string used to quickly identify certain events or conditions.
Values include:
REST
,
RemoteSupport
,
ZMQ
,
NDU
(non-
disruptive upgrades),
CC
(cluster creation),
LUN
,
System Journal Fields
73