View Issue Details

IDProjectCategoryView StatusLast Update
000024710000-011: Historical Accesspublic2012-02-10 16:57
ReporterPaul Hunkar Assigned ToEric Murphy  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.02 
Summary0000247: Check all Audit EventTypes for Services
Description

Some Services have changed (e.g. ActivateSession). The Audit EventTypes generated when the services are called where defined before the services have changed. We have to check if we need to add/change/remove properties of the Audit EventTypes based on the changes.

Additional Information

As part of this review discovered that the AuditUpdateEventType, which is to be used for a group of service, needs to have additional sub types defined. It was alsoo be used for Call services, but the call service do not fit into the patter defined by it. This will requires the addition of sever new Audit event types and will also effect other specification. (part 3, part 4, Part 10, Part 11)

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0000114 closedWolfgang Mahnke 10000-005: Information Model Check all Audit EventTypes for Services 

Activities

Paul Hunkar

2007-11-08 21:36

developer   ~0000474

Provided Updated Text to eric in the form of an e-mail also included here (but loose formating here)

Historical Audit Events

AuditEvents are generated as a result of an action taken on the server by a client of the server. For example, in response to a client issuing a write to a Variable, the server would generate an AuditEvent describing the Variable as the source and the user and client session as the initiators of the Event.
Servers must generate events of the AuditHistoryUpdateEventType or a sub-type of this type for all invocations of the HistoryUpdate service on any HistoricalNode. See [UA Part 3] and [UA Part 5] for details on the AuditHistoryUpdateEventType model and its sub models. In the case where the HistoryUpdate service is invoked to insert HistoricalEvents, the AuditHistoryEventUpdateEvent must include the EventId of the inserted event and a description that indicates that the event was inserted. In the case where the HistoryUpdate service is invoked to delete records, the AuditHistoryDeleteEventType or one of its sub-types must be generated. In particular a DELETERAW or DELETEMODIFIED must generate an AuditHistoryRawModifyDeleteEventType event or a sub-type of it, A DELETEATTIME must generate an AuditHistoryAtTimeDeleteEventType event or a sub-type of it, A DELETEEVENT must generate an AuditHistoryEventDeleteEventType event or a sub-type of it. All other updates must follow the guidelines provided in the AuditHistoryUpdateEventType Model.

Eric Murphy

2007-11-12 01:01

developer   ~0000499

Added text supplied by Paul H.

OPC UA Part 11 - Historical Access RC 1.01.07

Randy Armstrong

2010-08-31 16:41

administrator   ~0002082

Discussed in Telcon Aug 31st

Issue History

Date Modified Username Field Change
2007-11-08 21:32 Paul Hunkar New Issue
2007-11-08 21:32 Paul Hunkar Status new => assigned
2007-11-08 21:32 Paul Hunkar Assigned To => Paul Hunkar
2007-11-08 21:32 Paul Hunkar Issue generated from: 0000114
2007-11-08 21:32 Paul Hunkar Relationship added related to 0000114
2007-11-08 21:34 Paul Hunkar Project 10000-005: Information Model => 10000-011: Historical Access
2007-11-08 21:36 Paul Hunkar Note Added: 0000474
2007-11-08 21:36 Paul Hunkar Assigned To Paul Hunkar => Eric Murphy
2007-11-12 01:01 Eric Murphy Note Added: 0000499
2007-11-12 01:01 Eric Murphy Status assigned => resolved
2010-08-31 16:41 Randy Armstrong Status resolved => closed
2010-08-31 16:41 Randy Armstrong Note Added: 0002082
2010-08-31 16:41 Randy Armstrong Resolution open => fixed
2012-02-10 16:57 Jim Luth Fixed in Version => 1.02