Feature #44

Implement basic introspection support

Added by S. Wrede about 11 years ago. Updated almost 7 years ago.

Status:ResolvedStart date:03/24/2014
Priority:HighDue date:03/24/2014
Assignee:J. Moringen% Done:

100%

Category:Introspection
Target version:rsb-0.11

Description

Basic introspection will allow:
  • Being notified of created and destroyed participants ✓
  • Querying the currently existing participants ✓
  • Obtaining some information about participants such as id, scope, type, containing process, host ✓
    • Periodically re-querying participants to detect crashed processes ✓
  • Maintaining a list of remote processes ✓
  • Maintaining a list of remote hosts ✓
    • Maintaining estimated clock offsets for remote hosts ✓
    • Maintaining estimated communication latency for remote hosts ✓

Not sure about this old requirement statement:

It should be possible to subscribe to this kind of internal meta events in the same manner as we do for all other events.

It will certainly be possible to receive introspection events like ordinary events but that would entail knowing and sometimes (at least partially) implementing the introspection protocol. I (jmoringe) think a client API is more convenient and less error-prone.


Subtasks

Feature #1736: Implement participant creation and destruction hooksResolvedJ. Moringen

Feature #1737: Implement participant creation and destruction hooksResolvedJ. Wienke

Feature #1738: Implement participant creation and destruction hooksResolvedJ. Moringen

Feature #1739: Implement participant creation and destruction hooksResolvedJ. Moringen

Feature #1740: Implement introspection event senderResolvedJ. Moringen

Feature #1741: Implement introspection event senderResolvedJ. Moringen

Feature #1742: Implement introspection event senderResolvedJ. Wienke

Feature #1743: Implement introspection event senderResolvedJ. Moringen

Feature #1744: Implement introspection event receiver and client APIResolvedJ. Moringen

Feature #1748: Add introspection messages to protocolResolvedJ. Moringen

Feature #1749: Specify introspection protocolResolvedJ. Moringen

Feature #1750: Test introspection as part of integrationtestResolvedJ. Moringen

Feature #1751: Create introspection toolResolvedJ. Moringen

Tasks #1752: Document introspection toolResolvedJ. Moringen

Tasks #1822: Add method classesResolvedJ. Moringen

Feature #1823: Transmit start-time of processes in introspection messagesResolvedJ. Moringen

Feature #1827: Initial support for participant hierarchiesResolvedJ. Moringen

Feature #1828: Initial support for participant hierarchiesResolvedJ. Moringen

Feature #1829: Initial support for participant hierarchiesResolvedS. Wrede

Feature #1830: Initial support for participant hierarchiesResolvedJ. Moringen

Feature #1833: Remove crashed processes from database after a (configura...ResolvedJ. Moringen

Feature #1837: Include RSB version in process introspection informationResolved

Feature #1869: Realize ProcessInfo and HostInfo Backend in JavaResolvedJ. Wienke

Feature #1978: Include machine and (operating system) software types and...ResolvedJ. Moringen

Feature #2036: Include id of executing user in process informationResolved

Feature #2037: Estimate clock offset and commucation latency of remote h...ResolvedJ. Moringen


Related issues

Related to Robotics Service Bus - Feature #197: Generate events for changes of channel participants Closed 02/18/2011
Related to Robotics Service Bus - Enhancement #1876: Use service-provider system for participant classes Resolved 05/11/2014
Related to Robotics Systems Commons - Feature #1966: Add interface and implementations for gathering informati... Resolved 08/27/2014
Related to Robotics Service Bus - Tasks #1994: Specify JSON format for information exchange between Java... Resolved 09/14/2014
Related to Robotics Service Bus - Feature #340: Implement Distributed Namingservice Feedback 05/30/2011
Related to Robotics Service Bus - Enhancement #1976: Web interface for introspection Resolved 09/14/2014
Blocks Robotics Service Bus - Feature #228: Introspection / Nameservice Interface and Initial Tool Su... Closed 03/18/2011
Follows Robotics Service Bus - Tasks #1820: Remove "request" and "reply" components from scopes in rp... Resolved 03/22/2014

History

#1 Updated by J. Wienke about 11 years ago

  • Category set to C++

#2 Updated by S. Wrede about 10 years ago

  • Target version set to rsb-0.7

#3 Updated by J. Moringen almost 10 years ago

  • Subject changed from Implement Basic Introception Support to Implement Basic Introspection Support

#4 Updated by J. Moringen over 9 years ago

  • Target version changed from rsb-0.7 to rsb-0.9

#5 Updated by J. Moringen almost 9 years ago

  • Target version changed from rsb-0.9 to rsb-0.10

#6 Updated by J. Moringen almost 8 years ago

  • Target version changed from rsb-0.10 to rsb-0.11

#7 Updated by J. Moringen over 7 years ago

  • Category changed from C++ to Introspection
  • Status changed from New to In Progress
  • Assignee set to J. Moringen
  • % Done changed from 0 to 10

#8 Updated by J. Moringen over 7 years ago

  • Description updated (diff)

#9 Updated by J. Moringen over 7 years ago

  • Subject changed from Implement Basic Introspection Support to Implement basic introspection support

#10 Updated by J. Moringen over 7 years ago

  • Description updated (diff)

#11 Updated by J. Moringen over 7 years ago

  • Description updated (diff)

#12 Updated by J. Moringen about 7 years ago

  • Related to Enhancement #1876: Use service-provider system for participant classes added

#13 Updated by J. Moringen about 7 years ago

  • Description updated (diff)

#14 Updated by J. Moringen about 7 years ago

  • Related to Feature #1966: Add interface and implementations for gathering information about the current host and process added

#15 Updated by J. Moringen about 7 years ago

  • Related to Tasks #1994: Specify JSON format for information exchange between Javascript-client and introspection server added

#16 Updated by J. Moringen about 7 years ago

#17 Updated by J. Moringen almost 7 years ago

  • Related to Feature #340: Implement Distributed Namingservice added

#18 Updated by J. Moringen almost 7 years ago

  • Status changed from In Progress to Resolved

#19 Updated by J. Moringen about 5 years ago

#20 Updated by J. Moringen about 5 years ago

Also available in: Atom PDF