Search

29 result(s) for LogRecords

• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  4.1 Overview
  provide a standard manner for user access to this information. The LogObject returns LogRecords via the GetRecords Method . The LogRecords when they are generated, can also be sent as Events
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  5.1 Overview
  collects log messages and make them available to a Client . A LogObject can contain LogRecords that were generated internally. It can also contain LogRecords that result from Events that have ... LogObject instance is declared (see 6 ). The LogObject can also generate Events for LogRecords that were generated internally. The underlying storage of LogRecords is not defined. The LogRecords could
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  5.2 LogObjectType definition
  Defined in 5.4 O ConformanceUnits LogObject Base Optional MaxRecords defines the maximum number of LogRecords in a buffer associated with this LogObject . When this maximum is reached, a new LogRecord ... MaxRecords . Optional MaxStorageDuration defines the maximum time period that the LogObject will buffer LogRecords associated with this LogObject . LogRecords that are older than the maximum duration may be deleted
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  5.3 GetRecords Method
  GetRecords Method This Method allows a Client to retrieve LogRecords associated with this LogObject . The signature of the Method is described below, and the arguments are described in Table ... with the last LogRecord . EndTime must be equal to or greater than StartTime . No LogRecords more recent then EndTime are returned. If there are no LogRecords at EndTime , then
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  5.5 LogRecord structure
  Additional details for mapping of the severity defined for OPC BaseEvents to LogRecords is described in Table 9 . False EventType 0:NodeId Describes the specific type of Event. It corresponds ... Table 9 provides the Severity ranges that shall be used for LogRecords . Other specifications, vendors or end users may further subset these ranges or generate thier own names
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  5.6.3 TraceContextDataType Structure
  ParentSpanId (together with the SpanId ) allows for the creation of a tree of related LogRecords . The ParentIdentifier can be used to provide context information related to the parent. Table
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  5.6.4 Passing SpanStructure from a Client
  Server receives the optional AdditionalHeader , it uses the provided SpanConextDataType Structure when generating any LogRecords that are generated related to the Service invocation that provided the AdditionalHeader. It is possible
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  5.8 LogRecordMask DataType
  Value Bit No. Description EventType 0 Indicates if the EventType is returned in the LogRecords if available. SourceNode 1 Indicates if the SourceNode is returned in the LogRecords if available ... SourceName 2 Indicates if the SourceName is returned in the LogRecords if available. TraceContext 3 Indicates if the TraceContext is returned in the LogRecords if available. AdditionalData 4 Indicates
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  5.9 Relationships between LogRecords - A LogRecord Hierarchy
  Relationships between LogRecords - A LogRecord Hierarchy When generating LogRecords it is important that a context be associated with each LogRecord . This context information can be used to show a relationship ... between various LogRecords in a Server as well as relationships between LogRecords that are in different Servers . This context information is stored in the TraceContext field in the LogRecord
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  6.1 Concepts
  Concepts A LogObject that supports storing Events as LogRecords extends the behaviour of a LogObject by providing the capability to collect all Events that the parent Object receives that have
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  6.2 LogRecord EventType Mapping
  LogRecordStructure . Any Object that has a Reference to one of these EventTypes shall generate LogRecords in the LogObject related to the defined BaseLogEventType. Figure 6 - BaseLogEventType Additional EventTypes
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  7.1 Overview
  AddressSpace . The ServerLog is a well-known instance that, if implemented, provides all LogRecords for the Server . The Logs object provides a central folder from which all LogObject instances
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  7.2 ServerLog
  collects diagnostic information for a Server if it is provided . The ServerLog exposes all LogRecords available in the Server (this shall include all LogRecords in all other LogObjects
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  A.1 LogObject Server examples overview
  Another example is a Server that also support EventHistory and stores the LogRecords as part of a standard EventHistory (see A.2 ). Other examples include a system in which the LogRecords ... multiple stores one for each LogObjects (see A.5 ). There is an example in which LogRecords are forwarded by the device to an OpenTelemetry system (see A.4 ) and there is also
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  A.2 Event History Illustration
  Event History Illustration A Server that supports EventHistory , might just pull LogRecords from the EventHistory storage (i.e. no storage of LogRecords in any LogObject ). The Event history storage would include
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  A.3 Syslog storage illustration
  server. In this illustration, the local LogObject would only contain a minimum buffer of LogRecords . Figure A.2 - SYSLOG illustration This specification provides no mapping to SYSLOG record, but the required
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  A.4 Open telemetry Illustration
  which uses OpenTelemetry to collect log or trace information. For more detail on how LogRecords can be imported in OpenTelemetry see Annex C . Figure A.3 - OpenTelemetry Illustration
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  A.5 Vendor Specific Storage
  Each LogObject stores its own its own copy of the LogRecord, even if the LogRecords are the result of an event stream. Each LogObject would have its own limits ... storage. This storage would result in some LogRecords being stored multiple time, in separate LogObjects. Also the list of LogRecords in the ServerLog might not include all of the LogRecords
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  B.2 Diagnostic client
  Client can call GetRecords from the Server (s) that are reporting an issue. The LogRecords should provide detailed information allowing the maintenance worker / engineer to diagnose and correct the issue ... minimum storage), the diagnostic Client might periodically connect the small devices and collect the LogRecords . As an alternative the small device might just generate Events for the LogRecords
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  B.3 Analytic engine
  Analytic engine An analytic engine would periodically collect all LogRecords and store them for analytics. The diagnostic information may be collected in a cloud environment, where it can be analysed
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  C.1 Open Telemetry Overview
  Mapping to OPC UA Figure C.1 also illustrates how an OpenTelemetry system could collect LogRecords from an LogObject C.2 describes part of the mapping an import tool would have ... perform to convert LogObject LogRecords to OpenTelemetry records
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  C.2 Open Telemetry System Import
  Open Telemetry System Import If an OpenTelemetry system is importing LogObject LogRecords , the collector will need to pull information from the TraceContext field. This structure contains the TraceId and SpanId ... also contain ParentSpanId (if one was provided). The SpanId field is used to group LogRecords together. If the SpanId field is null, then for each unique entry in the GroupingId
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.2 AutomationComponentType definition
  obtain the log of activity related to this AutomationComponent . Events can be mapped to LogRecords ( see OPC 10000-26 ) for the LogObject. LogObject records can also be generated without ... generation of an Event . If the LogObject is supported, the AutomationComponent shall produce LogRecords for all calls of the EstablishConnections and CloseConnections Methods . The LogObject configuration would determine
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.2 ConnectionManagerType definition
  generation of an Event . If the LogObject is supported, the ConnectionManager shall generate LogRecords for all calls of the EditConnectionConfigurationSets and ProcessConnectionConfigurationSets Methods . When acting as a Client establishing Connections ... ConnectionManager shall generate LogRecords for all EstablishConnections calls, CloseConnections calls, and any related calls, including reporting of all errors (see 8.10 and 8.11 for the required LogRecord content. Reporting
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.3.2 Establishing Connections
  AuditEntryId as part of the Method invocation. If the ConnectionManagerLog is supported, the LogRecords for the EstablishConnections Calls shall include the following: SourceNode shall be the NodeId of the ConnectionConfigurationSet
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.8.1 Overview
  ConnectionConfigurationSet data modifications. If the ConnectionManagerLog is supported, the ConnectionManager shall produce LogRecords for each change. The LogRecord includes: The SourceNode shall be the NodeId of the Variable that
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  8.2 AuditUaFxEventType
  Audit Event being mapped to LogObject records. The mapping of these AuditEvents to LogRecords shall use the AdditionalData field to include fields of the AuditEvent . Subtypes of the AuditEvent will
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  8.10 EstablishConnectionErrorEventType
  results in the Event being mapped to LogObject records. If the LogObject is recording LogRecords , the ErrorCode and the ErrorCodeNode shall be included in the resulting LogRecord as AdditionalData
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  8.11 CloseConnectionErrorEventType
  results in the Event being mapped to LogObject records. If the LogObject is recording LogRecords , the ErrorCode and the ErrorCodeNode shall be included in the resulting LogRecord as AdditionalData