When you create your account, InOrbit will start with a default configuration, which tracks only a few attributes from your robots, such as CPU Usage, HDD Usage and Network Rate.
You can configure InOrbit to capture more meaningful attributes for your particular operation, such as additional system or robot metrics, sensor readings, software component vitals or application-specific values.
Any attributes you configure can then be used for real-time monitoring, to visualize their values over time, to track overall fleet status and to trigger notifications when something is not within expected values.
These configurations are managed in the Data Sources section of the settings screen, accessible through Menu > Settings:
InOrbit currently supports the following data sources:
You can monitor CPU usage, RAM usage, specific HDD partitions and network interfaces.
ROS Diagnostics values
If you use ROS and have nodes that publish values in the
/diagnostics_agg topics, InOrbit can be configured to pick up any of these values.
Custom key/value pairs
If you are using ROS and want to publish an arbitrary value from your robot, you can publish a
std_msgs/String message with the form
apples=10) to the
/inorbit/custom_data/0 topic on the agent.
Other types / non-ROS
InOrbit also supports additional and non-ROS data sources, which can be enabled per customer request. Please let us know about your need via e-mail at firstname.lastname@example.org.
In order to make it easier to configure, InOrbit lets you search over the data sources that it can discover from your robots. Simply start typing in the box to filter between the different network interfaces, HDD partitions, ROS Diagnostics tools or custom key/value pairs:
NOTE: In order for InOrbit to be able to discover the available data sources on your robot, it is important that the agent be running before you attempt data source configuration.