Understanding the vRealize Log Insight logging values collected from the Replica and Client nodes helps you quickly identify a transaction problem.
Concord Container Logging Values
vRealize Log Insight collects logs from the Concord container present within the Replica node.
Logging Value |
Description |
|---|---|
logtime |
Shows the time the log was collected in UTC. |
level:INFO |
Represents the Concord log level, which is informational. |
concord_replica_id:<4> |
Shows the unique Concord container ID within a blockchain. |
logger:concord.tls |
Shows the name of the user logged into the Concord container. |
thread:aaa |
Lists the Concord thread name. |
correlation_id:<1234> |
Shows the transaction correlation ID. |
sequence_num |
Shows the transaction correlation ID. |
file_line:TlsTCPCommunication.cpp:<1293> |
Shows the file and line of the log. |
method:bft::communication::ConnectionStatus bft::communication::TlsTCPCommunication::TlsTcpImpl:: getCurrentConnectionStatus(const bft::communication::NodeNum) |
Highlights the method where the log occurred. |
message:<Connection found from 34 to 3> |
Indicates a log-specific message. |
optional_data:{"primary":"3","path":"fast"} |
Shows the extensible data format for the log. |
service_name:concord |
Shows the Concord container or service name, which is the source of the log. |
consortium_id:<bd6b06dd-9438-43d9-a317-ce924f3e4d0a> |
Shows the unique global consortium ID. |
source:null |
Shows a vRealize Log Insight generated field. You can safely ignore this value. |
ingest_timestamp:<1593909929659> |
Shows the time in milliseconds since the UNIX epoch. |
timestamp:<1593909929659> |
Shows the time in milliseconds since the UNIX epoch. |
log_timestamp:<1593909929659> |
Shows the time in milliseconds since the UNIX epoch. |
event_type:untyped |
Shows a vRealize Log Insight generated field. You can safely ignore this value. |
replica_id:<f739218d-664a-471a-8068-2281ba9f204b> |
Lists the Replica node ID of the deployed VM. |
Daml Ledger API Logging Values
vRealize Log Insight collects logs from the Daml Ledger API present within the Client node.
Logging Value |
Description |
|---|---|
logtime |
Shows the time the log was collected in UTC. |
level:INFO |
Represents the thin replica client log level within the Client node. The log level is informational. |
concord_replica_id:<4> |
Shows the unique thin replica client ID within a blockchain. |
logger:concord.tls |
Shows the name of the user logged into the thin replica client container. |
thread:aaa |
Lists the thin replica client thread name. |
correlation_id:<1234> |
Identifies a transaction at the Daml Ledger API level. This log value is for debugging purposes only. |
sequence_num |
Identifies a transaction at the thin replica client level. This log value is for debugging purposes only. |
file_line:TlsTCPCommunication.cpp:<1293> |
Shows the file and line number of the log. |
method:bft::communication::ConnectionStatus bft::communication::TlsTCPCommunication::TlsTcpImpl:: getCurrentConnectionStatus(const bft::communication::NodeNum) |
Highlights the method where the log occurred. |
message:<Connection found from 34 to 3> |
Indicates a log-specific message. |
optional_data:{"primary":"3","path":"fast"} |
Shows the extensible data format for the log. The primary value indicates the primary thin replica client in the blockchain, and the path value indicates whether the thin replica client is on a fast or slow path. This log value is for debugging purposes only. |
replica_id:<f739218d-664a-471a-8068-2281ba9f204b> |
Lists the Client node ID of the deployed VM. |
