Search

Scope: Core (OPC-10000-*) All specs

34 result(s) for LogObject

OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.2 ServerCapabilitiesType

unsigned integer specifying the maximum number of parallel continuation points of the LogObject GetRecords method that the Server can support per session. The value specifies the maximum the Server
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

1 Scope

Events that can be used to collect diagnostic information in a system. The LogObject model and related Events , Methods and Datatypes are defined in this specification
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

4.1 Overview

information and 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 ... Events (see 6 ). The LogObject does not define how the information is stored, only how it can be collected and how it can be accessed. This allows a vendor
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

5.1 Overview

instance that 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 ... ConditionClassId or ConditionSubClassId of LogEntryConditionClassType that are reported by the Object on which the LogObject instance is declared (see 6 ). The LogObject can also generate Events for LogRecords that were
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

5.2 LogObjectType definition

UInt16 0:PropertyType O 0:HasComponent Method 0:ReleaseContinuationPoint 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 will trigger the deletion of the oldest LogRecord . If this Variable is not provided, then there is no Server published limit
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 ... PropertyType M 0:HasProperty Variable 0:OutputArguments 0:Argument[] 0:PropertyType M ConformanceUnits LogObject Base
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

5.4 ReleaseContinuationPoint Method

ReleaseContinuationPoint Method This Method allows a Client to release a LogObject ContinuationPoint that was returned to it. The signature of the Method is described below, and the arguments are described ... DataType TypeDefinition Other 0:HasProperty Variable 0:InputArguments 0:Argument[] 0:PropertyType M ConformanceUnits LogObject Base
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

5.5 LogRecord structure

this structure type is returned as a field in a structure in the LogObject GetRecords Method call. The structure is formally defined in Table 8 . Table 8 - LogRecord structure Name ... null NodeId. . Additional rules may be defined by other specifications that utilize the LogObject . True SourceName 0:String Provides a description of the source of the LogRecord , this could
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

5.10 LogRecordsDataType

LogRecordsDataType This structured DataType is used as the return DataType in the LogObject GetRecords Method call. The structure is formally defined in Table 19 . Table 19 - LogRecordsDataType structure Name Type ... DataType TypeDefinition Other Subtype of the 0:Structure defined in OPC 10000-5 ConformanceUnits LogObject Base
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

5.11 LogObject and Security

LogObject and Security The LogObject can include information that maybe sensitive or include security related information. LogObjects that contain security related information should not be made accessible to all users ... only to authorised users. A LogObject can restrict a Client 's access to the GetRecords Method using standard OPC UA security features. This all or nothing approach can work well
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 ... Alarms instance can be defined by PLC programs and exposed in a Server , the LogObject can collect Diagnostics or other trace information from PLC user program, not just from Server
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

6.2 LogRecord EventType Mapping

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 can be defined as needed ... also be used. The only requirement for an Event to be recorded in the LogObject is for the Event to have a ConditionClassId or SubConditionClassId of LogEntryConditionClass . The following describes
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

6.4 LogOverflowEventType

DataType TypeDefinition Other Subtype of the 0:BaseEventType defined in OPC 10000-5 . ConformanceUnits LogObject Overflow Events of this class are generated by Servers that support LogObjects . This Event indicates ... that the LogObject storage was exceeded before the MaxStorageDuration was reached. The SourceNode Property for Events of this type shall be set to the NodeId of the LogObject . The SourceName
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

6.5 LogEntryConditionClassType

ConditionClassType used to classify Events that are to be collected in a LogObject . The LogEntryConditionClassType is formally defined in Table 23 . Table 23 - LogEntryConditionClassType definition Attribute Value BrowseName LogEntryConditionClassType IsAbstract ... BrowseName DataType TypeDefinition ModellingRule Subtype of the BaseConditionClassType defined in OPC 10000-9 . ConformanceUnits LogObject BaseEvent
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

7.1 Overview

Overview The OPC UA LogObject model defines two well-known instances; ServerLog and Logs (see Table 24 and Table 25 and Figure 7 ). LogObjects may also exist in other locations ... LogRecords for the Server . The Logs object provides a central folder from which all LogObject instances can be found. Figure 7 - ServerLog & Logs illustration
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

7.2 ServerLog

Server Object defined in OPC 10000-5 HasTypeDefinition ObjectType 0:LogObjectType ConformanceUnits LogObject ServerLog The ServerLog is a LogObject that collects diagnostic information for a Server if it is provided
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

A.1 LogObject Server examples overview

LogObject Server examples overview The LogObject might be added to a specific Object that is part of a device model and stores records in a vendor specific manner ... system in which the LogRecords are buffered locally in a single store for several LogObject (see A.5 ) or in multiple stores one for each LogObjects (see A.5 ). There
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

A.2 Event History Illustration

just pull LogRecords from the EventHistory storage (i.e. no storage of LogRecords in any LogObject ). The Event history storage would include the ConditionClassId ( SubConditionClassId ) field in an event
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

A.3 Syslog storage illustration

Syslog storage illustration This example illustrates a possible implementation in which the devices generating LogObject information are sending the information to a central SYSLOG 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 fields for SYSLOG entries
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

A.4 Open telemetry Illustration

Open telemetry Illustration This example illustrates a possible implementation in which the device generate LogObject information are deployed in a system which uses OpenTelemetry to collect log or trace information
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

A.5 Vendor Specific Storage

Vendor Specific Storage The storage can be per LogObject (see Figure A.4 ). Each LogObject stores its own its own copy of the LogRecord, even if the LogRecords are the result ... event stream. Each LogObject would have its own limits for storage. This storage would result in some LogRecords being stored multiple time, in separate LogObjects. Also the list of LogRecords
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

B.1 LogObject Client examples

LogObject Client examples This section provides some examples of clients that could be using the LogObject . The first example is a possible standard diagnostic Client , the second example
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

B.2 Diagnostic client

system through status summary information that is outside of the scope of a LogObject . This might be HealthStatus information defined in the DI specification, or diagnostic information define
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
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.2 AutomationComponentType definition

definition of the AggregatedHealthType and the aggregation rules, see 9.1 . AutomationComponentLog exposes a LogObject for the AutomationComponent . The LogObject (see OPC 10000-26 ) can be accessed to obtain ... this AutomationComponent . Events can be mapped to LogRecords ( see OPC 10000-26 ) for the LogObject. LogObject records can also be generated without the generation of an Event . If the LogObject
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.7.2 ConnectionManagerType definition

ConnectionConfigurationSets ; it does not indicate the status of the Connections. ConnectionManagerLog exposes a LogObject for the ConnectionManager . The LogObject (see OPC 10000-26 ) can be accessed to obtain ... ConnectionManager . Standardised E vents that can be used to trigger records for the LogObject are defined in 8.9 and 8.10 . LogObject records can also be generated without the generation
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.2 AuditUaFxEventType

ConditionSubClassType to LogEntryConditionClassType , which results in the Audit Event being mapped to LogObject records. The mapping of these AuditEvents to LogRecords shall use the AdditionalData field to include fields
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.3 AuditConnectionCleanupEventType

ConditionSubClassType to LogEntryConditionClassType , which results in the Audit Event being mapped to LogObject records. The RemovedEndpoint and the RelatedEndpoint shall be included in the resulting LogRecord as AdditionalData
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.4 AuditUpdateMethodResultEventType

ConditionSubClassType to LogEntryConditionClassType , which results in the Audit Event being mapped to LogObject records. The StatusCodeId shall be included in the resulting LogRecord as AdditionalData
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.5 ConnectionConfigurationSetEventType

ConditionClassType or a ConditionSubClassType to LogEntryConditionClassType , which results in the Event being mapped to LogObject records. This applies to all subtypes of this EventType . The ConnectionConfigurationSetNode, the Name
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.9 EstablishConnectionErrorEventType

True References Node Class BrowseName Note Subtype of the 0:BaseLogEventType. ConformanceUnits UAFX ConnectionManager LogObject Events This EventType inherits all Properties of the BaseLogEventType . The ConditionClassId shall ... ConditionClassType or a ConditionSubClassType to LogEntryConditionClassType , which results in the Event being mapped to LogObject records. If the LogObject is recording LogRecords , the ErrorCode and the ErrorCodeNode shall be included
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

8.10 CloseConnectionErrrorEventType

True References Node Class BrowseName Note Subtype of the 0:BaseLogEventType. ConformanceUnits UAFX ConnectionManager LogObject Events This EventType inherits all Properties of the BaseLogEventType . The ConditionClassId shall ... ConditionClassType or a ConditionSubClassType to LogEntryConditionClassType , which results in the Event being mapped to LogObject records. If the LogObject is recording LogRecords , the ErrorCode and the ErrorCodeNode shall be included
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.19 ConnectionDiagnosticsDataType

associated with ErrorEndpoint1 . In some cases, this will just be a generic Bad. The LogObject should be used for additional detail and the sequence of steps. If the value ... associated with ErrorEndpoint2 . In some cases, this will just be a generic Bad. The LogObject should be used for additional detail and the sequence of steps. If the value
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

G.1 Diagnostics Client

provided in the ConnectionDiagnostics array to diagnose the issue. In other cases, the LogObject associated with the ConnectionManager would have to be used to retrieve the detailed error information. ConnectionState