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

Table 1. Journal field descriptions continued, ConfigurationCapture, Event, Import, PhysicalInventory

Page 74 highlights

Table 1. Journal field descriptions (continued) Type Name Default Default Default Custom Custom Custom Custom Custom Custom Default MESSAGE MESSAGE_ID OBJECT_AUDIT_LOGINUID, OBJECT_AUDIT_SESSION, OBJECT_CMDLINE, OBJECT_COMM, OBJECT_EXE, OBJECT_GID, OBJECT_PID, OBJECT_SYSTEMD_CGROUP, OBJECT_SYSTEMD_OWNER_UID, OBJECT_SYSTEMD_SESSION, OBJECT_SYSTEMD_UNIT, OBJECT_SYSTEMD_USER_UNIT, OBJECT_UID OBJECT_CURRENT_STATE_NAME OBJECT_HANDLE OBJECT_ID OBJECT_OPERATION OBJECT_SUB_TYPE OBJECT_TYPE PRIORITY Custom Custom Custom Default Default Default Custom ROOT_COMMAND_ID STATUS_CODE SUB_COMPONENT SYSLOG_FACILITY SYSLOG_IDENTIFIER SYSLOG_PID THREAD_NAME Description ConfigurationCapture, Event, RB (resource balancer), Import, PhysicalInventory, IDF (platform ID files), DATAMOBILITY, NETWORK, DataCollection, and Host. The message string for the entry in the systemd journal. Unique identifier of the message. Additional fields added automatically by the systemd journal. Current state name associated with the object. Unique identifier used to represent a resource managed within the cluster. Unique identifier of the object for which you want to retrieve information from the system journal. Type of operation associated with the object. The sub-type of the object for which you want to retrieve information from the system journal. Type of the object for which you want to retrieve information from the system journal. Journal message level. Valid levels are: • CRITICAL-Events that demand immediate attention. • ERROR-Events that indicate problems, but do not require immediate attention. • WARN-Events the provide a warning about potential problems or indicates that a component is not in an ideal state. • INFO-Informational messages that provide details on the running status and changes to the system. • DEBUG-Verbose status, such as progress or success messages. Context ID of the primary request. Status code that represents a response to a particular request. The sub-component associated with the message. Syslog compatibility field that contains the name of the facility. Syslog compatibility field that contains the unique identifier. Syslog compatibility field that contains the process identifier. Name of the thread logging the message. 74 System Journal Fields

  • 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
ConfigurationCapture
,
Event
,
RB
(resource balancer),
Import
,
PhysicalInventory
,
IDF
(platform ID files),
DATAMOBILITY
, NETWORK,
DataCollection
, and
Host
.
Default
MESSAGE
The message string for the entry in the systemd journal.
Default
MESSAGE_ID
Unique identifier of the message.
Default
OBJECT_AUDIT_LOGINUID,
OBJECT_AUDIT_SESSION,
OBJECT_CMDLINE, OBJECT_COMM,
OBJECT_EXE, OBJECT_GID, OBJECT_PID,
OBJECT_SYSTEMD_CGROUP,
OBJECT_SYSTEMD_OWNER_UID,
OBJECT_SYSTEMD_SESSION,
OBJECT_SYSTEMD_UNIT,
OBJECT_SYSTEMD_USER_UNIT,
OBJECT_UID
Additional fields added automatically by the systemd journal.
Custom
OBJECT_CURRENT_STATE_NAME
Current state name associated with the object.
Custom
OBJECT_HANDLE
Unique identifier used to represent a resource managed within the
cluster.
Custom
OBJECT_ID
Unique identifier of the object for which you want to retrieve
information from the system journal.
Custom
OBJECT_OPERATION
Type of operation associated with the object.
Custom
OBJECT_SUB_TYPE
The sub-type of the object for which you want to retrieve
information from the system journal.
Custom
OBJECT_TYPE
Type of the object for which you want to retrieve information from
the system journal.
Default
PRIORITY
Journal message level. Valid levels are:
CRITICAL—Events that demand immediate attention.
ERROR—Events that indicate problems, but do not require
immediate attention.
WARN—Events the provide a warning about potential
problems or indicates that a component is not in an ideal state.
INFO—Informational messages that provide details on the
running status and changes to the system.
DEBUG—Verbose status, such as progress or success
messages.
Custom
ROOT_COMMAND_ID
Context ID of the primary request.
Custom
STATUS_CODE
Status code that represents a response to a particular request.
Custom
SUB_COMPONENT
The sub-component associated with the message.
Default
SYSLOG_FACILITY
Syslog compatibility field that contains the name of the facility.
Default
SYSLOG_IDENTIFIER
Syslog compatibility field that contains the unique identifier.
Default
SYSLOG_PID
Syslog compatibility field that contains the process identifier.
Custom
THREAD_NAME
Name of the thread logging the message.
74
System Journal Fields