Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell PowerStore Service Scripts Guide

PDF

Field descriptions

The core logging framework relies on the systemd journal services provided by the underlying CoreOS operating system. In addition to the default fields available with systemd journal in CoreOS, there are custom fields available for use with the cluster. The following table lists the descriptions of all the fields available for use.

Table 1. Journal field descriptionsDescribes the different system journal fields and whether they are default of custom, field names, and related field descriptions.
Type Name Description
Default __CURSOR Unique identifier that describes the position of the entry in the journal.
Default __MONOTONIC_TIMESTAMP The monotonic clock timestamp indicating the time elapsed between a certain event and the time when the entry in the journal occurred.
Default __REALTIME_TIMESTAMP The wall clock timestamp indicating the point in time when the entry was logged in the journal.
Default _AUDIT_LOGINUID, _AUDIT_SESSION The session and login UID of the process from where the journal entry originates from.
Default _BOOT_ID The kernel boot ID of the boot in which the message was generated.
Default _CAP_EFFECTIVE The effective capabilities of the process from where the journal entry originates from.
Default _CMDLINE The command line of the process the journal entry originates from
Default _COMM The name of the process the journal entry originates from.
Default _EXE The executable path of the process the journal entry originates from.
Default _GID The group ID of the process the journal entry originates from.
Default _HOSTNAME The name of the originating host.
Default _KERNEL_DEVICE The name of the kernel device.
Default _KERNEL_SUBSYSTEM The name of the kernel subsystem.
Default _LINE_BREAK Indicates that the log message in the standard output/error stream was not terminated with a normal newline character.
Default _MACHINE_ID Machine ID of the host from where the journal entry originates from.
Default _PID The process ID of the process the journal entry originates from.
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, 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 that 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.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\