View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000550010000-005: Information ModelSpecpublic2020-03-05 12:002022-09-06 17:03
ReporterHock, Christian Assigned ToJeff Harding  
PriorityurgentSeveritytweakReproducibilityalways
Status assignedResolutionopen 
Summary0005500: Missing "EventDiagnostic"
Description

The below mentioned missing diagnostic information is valid for Events, Alarms and Conditions - to make it shorter it is just used "Event".

SubscriptionEventDiagnostic variables:

  1. How many "Events" could not be delivered because of internal error situations - e.g. OutOfMemory - during updating event fields for subscribed "EventTypes".
    • The number of lost events will be unknown for the client.
  2. How many "Events" could not be delivered because of insufficient access rights for subscribed "EventTypes".
    • The number of lost events will be unknown for the client.
  3. How many "Events" are discarded if DiscardOldest is false.
    • The number of lost events will be unknown for the client.

ServerEventDiagnostic variables:

  1. How many "Events" could not be created because of internal error situations - e.g. OutOfMemory - during creation of an "Event".
    • The "Event" will be lost for any client.
  2. Accumulated variables for SubscriptionEventDiagnostic (1., 2. and 3.).
    • To show an interested client how many events are lost for all subscribed "Events".

Thinking about using the subcscription related diagnostics do not work/fit, because of missing granularity of subscribed "Objects" - e.g. Server Object and all the different events it needs to "cover".

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jeff Harding

2020-06-29 18:53

developer   ~0012505

Does 'discardedMessageCount' in SubscriptionDiagnosticDataType cover the subscription cases? Do we really need a more detailed breakdown?

Jeff Harding

2020-06-29 18:53

developer   ~0012506

See notes below.

Hock, Christian

2020-06-30 08:41

developer   ~0012512

Today we are only able to write these DETAILED information in our internal DiagnosticBuffers - because our customers needs this information.
The idea is, that this information made public via OPC UA would improve OPC UA diagnostic and no vendor specific tools are needed to get a more detailed diagnostic information.

To anwer the question: We appreciate to get a more detailed breakdown.

Issue History

Date Modified Username Field Change
2020-03-05 12:00 Hock, Christian New Issue
2020-03-05 18:09 Jim Luth Assigned To => Hock, Christian
2020-03-05 18:09 Jim Luth Status new => assigned
2020-06-29 18:53 Jeff Harding Note Added: 0012505
2020-06-29 18:53 Jeff Harding Status assigned => feedback
2020-06-29 18:53 Jeff Harding Note Added: 0012506
2020-06-30 08:41 Hock, Christian Note Added: 0012512
2022-09-06 17:02 Jim Luth Assigned To Hock, Christian => Jeff Harding
2022-09-06 17:03 Jim Luth Status feedback => assigned