Difference between revisions of "uaCap:Robustness DiagData"

From UaCapabilities
Jump to: navigation, search
 
Line 1: Line 1:
 
{{CapabilityUri|/Robustness/Diagnostic-Data}}
 
{{CapabilityUri|/Robustness/Diagnostic-Data}}
 
'''Description'''
 
'''Description'''
<br>Objects with diagnostic information for numerous Server activities are supported.
+
<br>The collection of diagnostic information can greatly aid in early detection and prevention of potential problems.
 +
OPC UA defines Objects with diagnostic information for numerous Server activities.
 
<br>The collection of diagnostic information can be turned on or off so that it does not unnecessarily impede normal operation.
 
<br>The collection of diagnostic information can be turned on or off so that it does not unnecessarily impede normal operation.
  
Line 11: Line 12:
 
* Identify bad / inefficient interaction scenarios.
 
* Identify bad / inefficient interaction scenarios.
  
{{uaConformance|TBD <!-- Client -->|
+
{{uaConformance|
TBD <!-- Server -->
+
* Enable and disable collection of diagnostics.
<!-- Example
+
* Make use of diagnostic data.
* [http://opcfoundation.org/UA-Profile/Server/GlobalCertificateManagement '''Global Certificate Management Server Profile''']
+
|
* [http://opcfoundation.org/UA-Profile/Client/GlobalCertificateManagement '''Global Certificate Management Client Profile''']
+
* Support the diagnostic information model defined in OPC UA Part 5.
-->
+
 
}}
 
}}

Latest revision as of 07:51, 12 February 2015

URN:          https://opcfoundation.org/wiki/index.php/Robustness/Diagnostic-Data

Description
The collection of diagnostic information can greatly aid in early detection and prevention of potential problems. OPC UA defines Objects with diagnostic information for numerous Server activities.
The collection of diagnostic information can be turned on or off so that it does not unnecessarily impede normal operation.

Usage Considerations

  • Identify current load.
  • Identify security attacks.
  • Identify usage patterns.
  • Identify bottlenecks.
  • Identify bad / inefficient interaction scenarios.

Conformance Testing

Client Server
  • Enable and disable collection of diagnostics.
  • Make use of diagnostic data.
  • Support the diagnostic information model defined in OPC UA Part 5.